Technology Strategy Patterns — Episode 4

The 30 Second Answer respects the listener's attention. When an executive asks an unexpected question, state a position in no more than three points, support each with a reason or observable effect, and stop. Follow-up supplies the detail. In asynchronous communication, thirty seconds is reading time, not drafting time: status, recommendation, and next step should be visible at a glance. Prepare versions for predictable questions about project health, needed support, and your preferred decision.

Rented Brain changes the speaker's position. A technology leader adopts an independent consultant's distance: investigate without defending the current structure, surface unwelcome evidence, and recommend instead of evading. The conversation also warns against outsourcing strategy wholesale. A consultant's plan quickly expires when the organization neither joined the reasoning nor learned to make the next decision. The lesson is intellectual independence and candour while retaining ownership of consequences.

Ars Rhetorica describes three supports for a persuasive case. Logos leads from evidence to a conclusion that others can inspect; ethos establishes relevant competence and trustworthiness; pathos connects the choice to a tangible risk or a desirable future. Removing any one weakens the case, yet authority and emotion can easily become fallacies or theatre. A sound strategy therefore distinguishes observations from hypotheses, preserves the causal chain, and lets the audience test why the proposed intervention should produce its claimed outcome instead of asking them to accept confidence as proof.

Fait Accompli moves the hardest work from the formal presentation to conversations held before it. The proposer identifies everyone affected, meets key stakeholders individually, hears objections, and incorporates legitimate changes. By the main meeting, participants recognize a decision they helped shape, so the session can establish commitments instead of discovering conflict. The episode treats this as shared authorship rather than covertly selling a finished answer. If stakeholders were merely warmed up but had no influence, their polite agreement will disappear as soon as implementation imposes costs on their teams.

Dramatic Structure organizes architectural evidence as a journey: an initial condition and goal, a disruption, mounting consequences, an intervention, and a new organizational capability. That sequence helps people follow the stakes, but its claims still need metrics, and it must end with a specific ask for a decision, resource, or action. Without that ending, an audience may praise an engaging presentation and change nothing. Story structure is navigation through an argument; it does not license replacing calculation with spectacle or inventing a heroic victory unsupported by evidence.

Deconstruction challenges both a proposition and its opposite, exposing local optimization, hidden cost, and recurring work the organization has become good at handling rather than eliminating. Scalable Business Machine then widens the frame: describe the vision, customers, departments, activities, deliverables, valuable outcomes, principles, tools, roles, and measures as one system. Its value is not memorizing fifteen steps but connecting organizational design to customer value. Announcing the model is only a midpoint. Adoption, measurement, and repeated adjustment determine whether the designed machine operates outside the diagram.