Current-state architecture
We draw what exists, across all six layers, including the parts held together by one person’s memory. Almost no organization has this written down.
flagship capability
solutions architecture.
We figure out what needs to change and architect how it should work. Strategy, operations, technology, AI, people, and process are rarely separate problems. form.strategy looks at the whole system, identifies what is getting in the way, and designs the future-state architecture and the implementation path. Consulting and advisory are ways we engage inside this practice, not a separate door.
the failure we keep meeting
“We bought the software. It didn’t fix anything, because the problem was never only the software.”
six layers
what we design across.
A solution that only touches one of these moves the problem somewhere else. Most failed implementations are a technology answer to a process question.
01
People
Who owns what. Which decisions belong to which role, what capability actually exists today, and what the change will ask of them.
02
Process
How work moves. The sequence, the handoffs, the approvals, and the places where things quietly wait for someone who doesn’t know they’re holding it.
03
Technology
The platforms, the integrations between them, and the honest question of which existing tools stay, which go, and which were never the problem.
04
Data
Where it originates, who is allowed to touch it, where it is duplicated into contradiction, and whether anyone can trust the number in the report.
05
Intelligence
What the organization can see about itself, what it can predict, and where AI genuinely augments a decision rather than decorating a dashboard.
06
Experience
What all of the above feels like from the outside — to a customer, a guest, a member, or the staff member who has to live inside it every day.
how it works
the sequence.
Target-state architecture
What it should look like, why, and the trade-offs we deliberately accepted. Written so a second team could execute it consistently without us.
The path between them
Sequenced, with dependencies named and a first phase that delivers something real. Architecture that can only be adopted all at once never gets adopted.
what you get
in your hands.
Documents you own and can hand to any vendor, including one that isn’t us. That’s deliberate.
- Current-state architecture across all six layers
- Target-state architecture with named trade-offs
- Integration and data-flow design
- A sequenced implementation path with dependencies
- Decision records — what we chose and why
- A migration story if you outgrow any part of it
next step
describe the problem, not the product.
If you already know exactly which platform to buy, you may not need architecture. If you’ve bought three and it’s worse, you do.