Welcome to this week's Architectural Challenge, with focus on Strategic Thinking.

‍

If I had to use one word to describe the role of an architect, it would be: Clarity. Not technical brilliance. Not coding skills. Clarity.

And the challenge I teased in my previous email? It's a masterclass in finding clarity in ambiguity through pattern matching.

‍

"Your client needs credit card processing in Salesforce, but their current payment gateway has no managed package. Evaluate the impact of changing payment gateways.”

(220.301 - Solution Architecture Strategy)

‍

You could workshop this for hours. Or you could recognize the pattern in 30 seconds.

‍

This is exactly the kind of exercise we drill in our CTA Coaching—because an architect's real edge isn't just technical depth, it is clarity and speed in the face of ambiguity.

‍

The difference? Use Cases and Mental Models - two tools that transform ambiguity into clarity. (We drill these relentlessly in our programs, and now you'll see why.)

‍

So what's the general use case here? Take a moment. What pattern do you see?

‍

“Implement a managed package for credit card payments.”  Too narrow. You're stuck in the specifics. One of the deadly sins of technical experts.

‍

“Replace payment processor with one that has a managed package.” Better, but still too specialized. Go broader.

‍

"Replace a legacy system with one that directly integrates with Salesforce." NOW this is what thinking like an Architect means. This pattern appears everywhere.

‍

Now, this might seem like a basic example. And it is, but it works like a charm to demonstrate the universal power of this approach.

‍

Once you see it, you can't unsee it. And you'll know exactly what to evaluate. 

‍

Recognizing the pattern is step one. Building the mental model is step two. Once you have both, your brain automatically knows what to evaluate and you just fill in the blanks.

‍

This is true AI - Architecture Intelligence. Not memorizing specs. Not knowing every API. It's pattern matching and resolution.

‍

So when you see 'replace legacy system with Salesforce-integrated solution,' what areas need evaluation?

‍

Take 10 seconds. List them out.

‍

• Vendor selection - Vendors must be evaluated and selected
• Business processes - Must be revised to align with new solution
• Users - Require communication and training
• Dependencies - Other systems dependent on the legacy system and processes must be identified and updated .
• Data migration - Legacy data must be migrated and references updated
• Reporting - Reports and analytics might be impacted
• Change management - Depending on the magnitude, you might need a separate project, not just a user story
• Timeline - Project timelines affected by all above factors

‍

Notice what just happened?

‍

We took a specific, ambiguous problem, identified the essential use case, and applied a mental model to resolve it. This is Architecture Intelligence in action.

‍

Mental models are your maps. They provide clarity and tell you where to dig deeper.

‍

Have we fully answered “What's the change impact?” Not completely. But we know enough to say it's significant - and more importantly, we know exactly what to evaluate next if necessary.

‍

Want this superpower across all architectural challenges?

Join 78+ CTAs who've mastered Architecture Excellence.

Learn more and secure your spot

‍

Here's your homework:

Take your biggest current or past architecture challenge. Abstract it to its general use case. What pattern does it match? Build your mental model.

‍

Next week:

Another pattern hidden in plain sight: When 'Lead or Account?' is actually asking the wrong question entirely.

‍

Seb

‍

PS - For the neuroscience geeks: Pattern recognition literally rewires your brain. Once you see these patterns, you can't unsee them. Check out 'Things You Cannot Unsee' in The Atlantic if you want to go deeper

Things You Cannot Unsee (and What They Say About Your Brain) in The Atlantic.