Two Doors
How a Power Platform architect decides when the team is split five against five — and how to live with the call afterwards.
The room is split. Five engineers favour one approach; five favour the other. Both camps are senior. Both have written paragraphs of justification on the whiteboard. They are now looking at you. The build cannot start until the architect speaks.
This is the moment that does not appear in any training course. There is no obviously correct answer — if there were, the team would have found it together. There is no winning argument — if there were, one camp would have already conceded. The architect is not being asked to discover the truth. The architect is being asked to convert disagreement into momentum without losing the trust of the five who will be told to commit to the path they did not choose.
Done badly, the call wastes a quarter. Done well, it becomes the moment the team began to trust the architecture function. Here is the framework I bring to it.
Section OneReframe the Question
The first mistake architects make in this situation is treating the 5-5 split as a technical contest with a right answer. It almost never is. When two competent groups of senior engineers reach opposite conclusions from the same evidence, the technical merit of the two paths is, within a margin, close to equal. They are arguing because the tiebreaker is missing — usually a requirement, a non-functional constraint, or a value judgement nobody has surfaced.
The architect's job is not to declare a winner. It is to:
- Find the missing question. What requirement, if known, would collapse the disagreement? Surface it. Make the business answer it. Then both camps converge.
- Classify the door. Borrow from Jeff Bezos. A two-way door can be reversed in a week with limited damage. A one-way door is structural and cannot be unwound without a project. Apply scrutiny proportional to the door type. Spending three weeks deciding a two-way door is its own kind of failure.
- Make the call, then defend the process — not the choice. A team will accept a decision it would not have made, if it trusts the way the decision was reached.
Section TwoThe Anchor Example
To keep this concrete, let us use a dilemma that actually happens. Your Power Platform team is building an opportunity-management solution in Dataverse. Every new Opportunity must trigger the creation of a matching customer record in SAP. The team is split.
A Dataverse Plugin in C#
- Synchronous & transactional. If SAP rejects the customer, the Opportunity save fails. Strong consistency by design.
- No per-execution license cost. Plugin runs inside the Dataverse sandbox; no premium flow runs to count.
- Sub-second latency. Direct HTTP call from the plugin to SAP, no orchestrator overhead.
- Testable. Unit-testable with FakeXrmEasy; mockable interfaces.
- Familiar territory. Half the team comes from a Dynamics CE background and has shipped plugins for years.
A Power Automate Cloud Flow
- Visual run history. Every execution is inspectable end-to-end; a citizen developer can diagnose a failure.
- Built-in retry & error handling. Native retry policies, "configure run after," scopes for compensation.
- Faster to MVP. First working sync in a day, not a sprint.
- Easier to evolve. When SAP adds a field, a maker changes it without a build pipeline.
- Roadmap alignment. Microsoft's investment is heaviest in low-code; the platform documentation, Copilot, and CoE tooling all assume flows by default.
Read those two columns carefully. Neither is wrong. Neither camp is being unreasonable. The disagreement is real, and the room is genuinely split, because the actual tiebreaker has not been put on the table. We will return to this example after laying out the framework.
Section ThreeThe Nine Decision Factors
I weigh every contested architectural decision against nine factors, grouped into three horizons. The grouping matters because each horizon imposes a different kind of cost — and architects who only consider one horizon make the predictable mistakes of their training.
Time to first value
How fast can each path show a working end-to-end demo? A faster path buys you political room to iterate.
Team skill availability
What can your current team actually ship? Plans that require hiring or reskilling are bets, not decisions.
Build & license cost
Premium connector entitlements, AI Builder / Copilot Credits, per-user and Process licensing — count what each path consumes.
Maintainability
Who will hold this in eighteen months? Will they read C# plugin code or a flow diagram more confidently?
Performance & scale
What is the throughput envelope? Where does the path fall over — 1,000 records a day, or 100,000?
Observability & support
When it fails at 2 a.m., what does the on-call see? Run history, App Insights traces, or silence?
Reversibility
Two-way door or one-way door? How many weeks would it cost to undo the choice if you were wrong?
Platform alignment
Does the path ride Microsoft's roadmap or fight it? Roadmap-aligned choices age into "best practice"; off-roadmap choices age into technical debt.
Strategic optionality
Which path keeps more doors open for next year's scope? The decision that preserves choice usually wins on a long enough timeline.
Section FourThe Framework Applied
Returning to Door A (plugin) versus Door B (cloud flow), here is how I would mark the nine factors before turning to the room. The verdict in each row is a tentative one — its strength depends on facts only the business can supply.
| Factor | Door A · Plugin | Door B · Flow | Tentative edge |
|---|---|---|---|
| Time to first value | Sprint or two | Within days | Door B |
| Team skill | Strong if half are CE-trained | Universal across the team | Door B |
| Build & license cost | No per-execution cost | Premium connector + flow runs | Door A |
| Maintainability | Compiled, signed, deployed | Visible, editable by a maker | Door B |
| Performance & scale | Sub-second, sandboxed | Async, throttled, retries | Door A (high volume) |
| Observability | Trace logs, App Insights | Native run history per record | Door B |
| Reversibility | Plugin assembly redeploy | Disable a flow toggle | Door B |
| Platform alignment | Mature, but de-emphasised | Microsoft's low-code default | Door B |
| Strategic optionality | Locks into pro-code path | Easy to extend to other targets | Door B |
Door B wins seven of nine. A junior architect would call it here.
A senior architect would not — because the table assumes a missing answer. Look again at row five and row seven. Both are conditional on the same question: what consistency does the business actually require? If a new Opportunity may not exist in Dataverse without a matching customer in SAP, the requirement is strong consistency. A flow cannot provide that. Door A is then the only acceptable answer, and seven low-priority wins by Door B become irrelevant.
This is the architect's actual contribution: not the table, but the recognition that the table is incomplete without one missing fact. That recognition turns a 5-5 deadlock into a thirty-minute conversation with the product owner — and a decision the room can accept.
Ninety percent of contested architecture decisions resolve cleanly the moment a missing non-functional requirement is named. The architect's first action is rarely to choose — it is to elicit the choice from a stakeholder who did not realise they were holding it.
Section FiveOther Tiebreakers Worth Practising On
The same framework applies to most Power Platform 5-5 splits. Each of these is a real argument I have refereed, and each resolved on a single missing question.
Section SixHow to Run the Room
The framework is the easy part. The harder skill is choreographing the conversation so that the team leaves with conviction instead of resentment. I run the meeting in six moves.
- Make each camp argue the other side first.Ten minutes. Camp A presents Door B as if it were their own. Camp B does the inverse. This collapses straw-man positions and surfaces the strongest version of each path. A surprising number of disagreements end here.
- Surface the missing requirement out loud.Walk the room through the nine factors. Where the table is contested, name the underlying business question. Refuse to proceed until it is answered or explicitly deferred with a default.
- Classify the door.Two-way or one-way? Reversible in a week, or structural? Match the depth of analysis to the cost of being wrong. Two-way doors should be decided in the meeting; one-way doors deserve a memo and a sleep.
- Time-box the decision."We will choose by end of day Wednesday." Without a deadline, the room re-litigates. With a deadline, both camps focus on what would change their mind.
- Document the rejected alternative.An Architecture Decision Record (ADR) captures the choice and the reason the other path was not taken. This is gold in eighteen months when somebody asks "why didn't we use a flow?"
- Name the rollback criteria."If sync latency exceeds 30 seconds at p95 for two consecutive weeks, we revisit." A decision with explicit reversibility is easier to commit to than one that feels permanent.
Beware the cop-out "let's do both." Sometimes — backbone-plus-bespoke patterns, hybrid integrations — that is the right answer. More often, it is the architect's way of avoiding the unpopularity of a clear call. If "both" doubles your maintenance surface to halve a political argument, you have not led, you have flinched.
Section SevenAfter the Call
The hour after the decision matters as much as the hour of the decision. Three behaviours separate architects who keep their teams from those who slowly lose them.
- Disagree and commit, publicly. Borrow the phrase from Bezos and Andy Grove. Acknowledge the dissent. Acknowledge the merit of the rejected path. Then ask the dissenting five to commit fully to execution. The architect's tone — gracious, specific, unambiguous — sets whether the team rallies or sulks.
- Write the ADR within 48 hours. Memory of the trade-offs decays faster than you think. The ADR is the artefact that lets a future architect — possibly you, possibly your successor — reverse the decision intelligently when the world changes.
- Schedule the 90-day review. Put a calendar invite on the books now. Tell the team: "If this turns out to be wrong, here is the moment we will say so." That single act removes the unspoken fear that the decision is a tomb.
Architecture decisions made this way do something that pure technical decisions cannot: they build the muscle of collective decision-making under uncertainty. The next 5-5 split is easier. By the fourth one, the team has internalised the framework and resolves most of them without needing you in the room.
That is the quiet measure of architectural leadership — not the cleverness of any single call, but the steady reduction of how often the team needs you to make it.