From Paralysis to a Plan
When the way architecture gets done shifts this fast, the natural response is to freeze. Paralysis to a Plan applies the NovoCircle Method, the four questions at the heart of The Value Shift, to your practice and turns that standstill into a plan you and your team can act on.
(opens in a new tab)
The NovoCircle Method
Movement beats planning
Most leaders freeze when the ground shifts. They reach for tools built for a different era, which assumed months to analyze, committees to consult and a stable environment. For an architecture practice adopting AI, none of that exists anymore.
A stopped car cannot be steered. Once it's moving you can turn, speed up or change course.
The NovoCircle Method is how we get it moving. It distills enterprise architecture, project management, business analysis and quality-improvement frameworks down to the four questions they all share.
Four questions that turn paralysis into a plan
This is the structure of a Paralysis to a Plan engagement. We work through the four questions in order. The sequence keeps a practice from spinning.
What is the problem you're trying to solve?
Practices skip this question, and it is the most expensive mistake they make. Teams jump straight to action, buying AI tools, standing up a pilot or reorganizing, before they've named the underlying problem. Six months later they wonder why nothing got better.
"Leverage AI" is the clearest example. Architecture teams launch experiments because they feel behind. Most deliver thin results because they never defined the specific problem they were solving. Without that anchor, even the most capable tool becomes noise.
We break the cycle with one sentence: this is the specific problem we're trying to solve.
What are the pieces of the puzzle?
Once the problem is named, we unpack the context around it: your Sparx EA deployment, repository structure, metamodel governance, data quality, the enterprise data your architects depend on, your AI platforms and policies, and the skills your team has versus the ones the work needs.
This is where the five factors come in. They are the questions that determine which AI approach fits: the type of architecture you do, the use cases with the most immediate impact, where your data comes from, the policies that constrain you, and where your architects are most comfortable working. Most pieces won't matter, and naming them is how you set them aside. The relevant few are what the plan gets built around.
What does success look like?
Most leaders spend more time cataloging what they don't like than naming what they want. We envision the future you're trying to create, and anchor it to a real date. That turns a wish into a plan. The anxiety doesn't disappear, but it stops running the room.
We make it concrete with a simple exercise: write the announcement you'd make once you've succeeded: "By [date], we have [specific result]." That document becomes your anchor. Every decision, opportunity and distraction gets held against it. Does this move us toward the date and outcome, or away from it?
What are the options for getting there?
With the problem named, the pieces laid out, and a time-bound target in place, the options surface. Notice the plural: options. There's always more than one way to get from where you are to where you're going, and the teams that jump to one tool first almost always choose the wrong one.
We look at the full range first: which AI-Augmented Architecture use cases, and which technical paths on Sparx EA. Then we choose based on where you need to go, weighed by impact rather than emotion or urgency, so the highest-impact move comes first.
Then we pressure test it
The method pays off most when you run it across several scenarios, including the less likely ones. This is anticipatory scenario planning, the companion move to the four questions. The questions get you moving. Scenario planning keeps you from being caught off guard when things shift again.
We map the range of outcomes. Best case, your team adopts faster than your peers and the practice's influence expands. Harder case, budgets tighten or a reorg lands mid-transition. The most likely sits somewhere between.
We find a viable path through each scenario. When one shows up, you already know what you'll do, and the moment lands as a data point rather than a crisis.
What this conversation looks like in practice
An illustration of the method applied to a real-shaped architecture problem. An EA practice team at a logistics company wanted to "use AI to be more productive."
The problem
Asking what was actually breaking right now surfaced it: architects were spending most of their week transcribing what they saw into the tool and pulling data from other systems by hand, leaving little time for the analysis and stakeholder conversations that create value.
The pieces
Repository structure, the data-governance policies that applied, the team's skills, the AI platforms already approved, and what they'd tried and abandoned. Most turned out to be constraints that ruled options out, which is what they are meant to do.
What success looks like
Cut current-state modeling time in half within two quarters. That number and date ruled out a multi-year platform overhaul and pointed straight to the Modeling and Analysis use cases on tools already in their stack.
The options
Three candidate projects, each scoped for effort, risk and impact. Two qualified as quick wins, and work started within three weeks.
We start the movement with you
Most teams are stuck because no one has sat down with them to name the actual problem, identify what matters and put a real date on what success looks like. A leader has to start that work, and we do it alongside you.
We run the four questions with you and your team as a conversation. The people side is usually the hardest part of the transition, and once the questions are in the room, the room changes.
You become the leader who gives people a way through, and we can stay by your side for every step that follows.
Scoped to you
Right-sized to your practice, for you or for you and your team. Scope is agreed up front.
Run as a guided conversation
Sparx EA deployment and data assessment
Use cases and technical options that fit your team
A prioritized, phased roadmap you keep
Executive summary for leadership
We can stay by your side to execute