What happened when I gave my Salesforce team real architects

Jessie Grenfell
Jessie Grenfellโ€ข

What happened when I leveraged our Solutions and Technical Architects' (now my CPO and CTO) strengths within my last Salesforce team.

โฌ†๏ธ The whole team's velocity improved. Before anything went into development, the architects provided a roadmap based not only on technical expertise, but their tribal knowledge of the system and business. That intentionality helped us get to the right solution faster and thoughtfully delegate work for features across our mixed team of developers and declarative admins. Developers were both unblocked and mentored in regular pair programming sessions with an architect, admins having that support from me.

๐Ÿ’ช๐Ÿป Stability increased. Formal technical architecture meant spreading that expertise that prevents bugs, enables scalability and ensures security to all efforts and not just the ones the architects hands-on developed. Formal business analysis meant thoughtful definitions of acceptance criteria, ensuring development resources weren't wasted solving the wrong problems. UX oversight of all development benefit the business in countless ways.

๐Ÿ˜ Team job satisfaction increased. This was a fast-paced environment with aggressive, arbitrary deadlines for continually re-prioritized and re-scoped demands. Anyone with experience in software development (or life, really) reads the burn-out and frustration inherent there. We couldn't control corporate culture, but instilling professionalism and strategic thinking into how we worked together was quantified by my team's surveyed job satisfaction doubling.

The experience mirrored what I found in my 15 years Salesforce consulting prior. Many of my clients had employees dedicated to building in Salesforce, from a single admin to full development teams. By nature and desire I am collaborative, I was not there to one-up or replace them. (I've seen that model, it's toxic.)

Beyond helping achieve business goals directly, I often enabled the teams I worked with- extendible Apex solutions and frameworks that smoothed development, coded solutions that included no-code configuration for non-developer admins to extend and maintain without me, SOPs that helped teams work cohesively.

Codality's fractional architecting gives you 3 architects โ€“ Principal, Technical and Solutions โ€“ in one engagement, giving a full suite of skills to facilitate your team however they need.

๐Ÿ“ฉ Message me if your team could use architectural assistance but doesn't need a ful-time architect quite yet.

#Salesforce #FractionalArchitect #SalesforceArchitecture #SalesforceDevelopment #TechnicalDebt #Codality #SolutionArchitecture #FinancialServices #ApexDevelopment

Jessie Grenfell

Jessie Grenfell

Jessie has spent 20+ years architecting and delivering software for organizations where complexity is the norm โ€” financial services, insurance, nonprofits, and regulated industries where getting it wrong isn't an option. She specializes in the hard problems: unique operational workflows, cross-system integrations, and the kind of compliance requirements (HIPAA, CCPA, SOC 2) that most developers treat as someone else's job.

At Codality, she leads every principal engagement from discovery through delivery โ€” because she's seen what happens when that thread gets cut.