DISCIPLINE THREE · OUTWARD FACING
The Architect
Design solutions the whole organization can succeed with.
The Architect is the third discipline in The Presales BOAT System™. It designs for everything a solution touches, so the solution still looks successful a year after go-live.
What does the organization around this solution need to succeed?
Architecture is bigger than the diagram
Ask a room full of Solution Consultants to define architecture and most will describe a diagram, with boxes, arrows, an API here, and a data flow there. That’s architecture in the smallest sense of the word, and it’s the sense that gets teams into trouble.
The Architect sees a bigger system. Business objectives, people, process, technology, security, governance, economics, delivery, and adoption are all connected, and they all trade off against each other once the solution leaves the whiteboard. A technically elegant design that ignores how it will be delivered, paid for, or adopted is only part of the picture.
The work runs across people as well as systems. More enterprise deals fail over disagreement than over technology, so part of the Architect’s job is translating between Operations, IT, Security, and Finance until they agree on what success should mean. Like the Trusted Advisor, the Architect faces outward, toward the customer.
STORY FROM THE FIELD
The Project Where Every Box Was Green
A healthcare provider network was replacing part of its patient access workflow with a new cloud platform, and by every measure the evaluation had gone well. The platform passed its functional requirements. APIs were validated, identity worked, and the call flows had been tested twice. Security approved the design. On the readiness review, every major component had a green box beside it.
The platform went live on schedule. Within two weeks a new exceptions queue had filled up, agents had started routing around it, and Operations had built a spreadsheet to track the work the system was supposed to handle. By the first quarterly review, the new platform was being blamed for creating complexity.
Every component had passed. What failed, and the question the project manager asked at her next readiness review, is where Chapter 13 begins.
What’s inside the Architect chapters
Five chapters move from seeing the whole system to designing a solution that survives a regulated enterprise.
13
See the Whole System
The Nine Dimensions · Nine-dimension architecture pressure test
14
Let the Outcome Choose the Architecture
The Opportunity Heatmap · Opportunity Heatmap scoring sheet
15
Design for What Happens After
The Assumption & Ownership Register · Architecture Assumption & Ownership Register
16
Design the Proof Together
Seven Map-the-Room questions · Map-the-Room worksheet and POC success-criteria one-pager
17
Design for the Real World
What it takes for a solution to survive a regulated enterprise at scale
A solution succeeds when the organization is built to support it.
The Elite Solution Consultant covers all five Architect chapters alongside the Builder, Operator, and Trusted Advisor, with the stories, models, and tools behind the BOAT System.