14.1 Documenting Business Needs, Agency Value & Vision for Desired Outcomes

14.1 Documenting Business Needs, Agency Value & Vision for Desired Outcomes

Exam Focus: The official outline's very first objective under the 45%-weighted product knowledge domain is "Document and articulate the business needs, value, and vision of the customer to support their desired business outcomes." There is no feature named in that sentence. It is a consulting objective, and it is the reason AP-222 scenarios so often open with two paragraphs about an agency's mandate before they mention a single object. Candidates who skim to the technical requirement and pick the most powerful component routinely fail these items, because the correct answer is the one traceable to the stated outcome.

---

Why Public Sector Value Is Not Commercial Value

A consultant arriving from a Sales Cloud or commerce background will reach for pipeline, conversion, and revenue per customer. None of those exist here. Agencies are not trying to grow a market; they are trying to discharge a statutory duty to a population they cannot choose and cannot refuse.

That last row deserves emphasis, because it is where Public Sector Solutions makes its strongest argument. When a legislature changes a fee schedule or an eligibility threshold, an agency running hard-coded logic files a change request, waits for a release, and regression-tests. An agency running Business Rules Engine expression sets and decision matrices versions the rule and activates it. "Days to implement a statutory change" is a genuine, defensible, agency-specific value statement — and it is the kind of sentence the exam rewards.

---

The Anatomy of a Defensible Benefit Statement

A benefit an agency can put in front of an oversight committee has four parts. Missing any one of them turns it into marketing.

The baseline is the part agencies most often cannot supply

Many agencies genuinely do not know their own cycle times, because the legacy system never measured them. When discovery finds no baseline, the correct move is not to invent one and not to abandon the benefit. It is to instrument the baseline as an early deliverable — capture the current-state measure during the first phase so the benefit becomes provable later. An architect who writes "baseline unknown; to be established in phase 1 via operational reporting" is doing the job correctly. One who writes "expect a 60% improvement" without a denominator has written a number that will be challenged the first time it reaches an auditor.

---

From Vision to Traceable Design

The deliverable that keeps a design honest is a value traceability chain. Every configuration decision should be walkable back to a mission outcome:

Mission outcome  ->  Business need  ->  Capability  ->  Configuration  ->  Measure

Worked example for a state grants office:

The chain is what lets an architect answer the hardest question in a government steering committee: "why are we paying for that?" If a configuration cannot be walked back to a mission outcome, it is scope that should be challenged — and on the exam, an option that adds capability with no stated outcome behind it is usually the distractor.

---

Where the Vision Comes From in a Government Engagement

Unlike a commercial client, a public agency rarely gets to invent its own vision. It inherits one. Discovery should locate it in these documented sources rather than in a workshop whiteboard:

• Enabling legislation and regulation — the statute that creates the program defines who is eligible, what the deadlines are, and what must be recorded. This is not a nice-to-have input; it is a constraint that outranks stakeholder preference.
• The agency's published strategic plan and performance report — most agencies publish measurable annual targets. These are pre-agreed success measures, and using them is far stronger than inventing new ones.
• Budget requests and appropriations language — an agency that received funding for a specific modernization has already written its own business case; align to it.
• Audit findings and oversight reports — an inspector general or auditor finding is the most reliable statement of a business need that exists, because the agency is already obligated to remediate it.
• Constituent-facing service standards — published commitments such as "we respond to public records requests within 10 business days" are ready-made targets.

---

Documenting It: What the Artifact Actually Looks Like

The expected output of this objective is short and specific, not a hundred-page deck:

1. Vision statement — one or two sentences in the agency's own language, expressed as a constituent outcome. "A contractor can obtain a routine commercial permit online in under three weeks without visiting the counter."
2. Business needs register — each need with its source (statute, audit finding, strategic plan), its owner, and its priority.
3. Value case — the baseline / target / mechanism / owner table above, one row per benefit.
4. Success measures and instrumentation plan — how each measure will actually be captured after go-live, which for most agencies means naming the reports, dashboards, or fields that will carry it.
5. Explicit non-goals — what this phase will not do. In government engagements, written non-goals prevent the mid-project scope expansion that consumes the contingency budget.

Two failure modes to recognise on the exam

• The product-first answer. An option that opens with a component name ("implement OmniStudio to modernize intake") without connecting to the stated outcome is almost always wrong when the stem spent a paragraph describing a mandate.
• The unmeasurable benefit. "Improved constituent experience" is not a benefit; "portal self-service rate rising from 12% to 55%, reducing counter visits" is. If two options are technically equivalent, the exam prefers the one tied to a measure.

---

💡 Real-World AP-222 Exam Scenarios & Case Analysis

Scenario 1: A Mandate With No Numbers

A state environmental agency has been directed by new legislation to issue air-quality permits within 90 days of a complete application, with penalties for missed deadlines. The agency cannot currently say how long permits take, because status is tracked in a shared spreadsheet. Leadership asks the implementation partner to "prove the return on investment" before approving the project.

How should the architect proceed?

• Anchor the value case to the statutory deadline, which is the strongest possible target: it is externally imposed, non-negotiable, and already carries a penalty.
• Acknowledge the missing baseline in writing rather than estimating one, and make baseline instrumentation a phase-1 deliverable — standard reporting on application receipt-to-decision duration from the first release.
• Express the mechanism concretely: replacing spreadsheet status with IndividualApplication and BusinessLicenseApplication lifecycle stages makes cycle time measurable; Action Plans make required review steps explicit; parallel departmental review removes the sequential wait.
• Name the accountable owner and the dashboard that will report it monthly.

Scenario 2: The Stakeholder Wish List

During discovery for a benefits agency, a program director asks for a mobile app, a chatbot, predictive analytics on fraud, and integration with six state systems. The agency's published strategic plan names one target: reduce the average benefit determination time from 32 days to 10 days.

What does the architect do with the wish list?

• Map every request against the single published outcome. Requests that shorten determination time (guided intake, rules-based eligibility determination, document completeness tracking) enter the phase-1 scope with a stated contribution.
• Requests that do not — the fraud analytics and four of the six integrations — are captured in the needs register with their source and priority, and explicitly listed as non-goals for this phase. They are not refused; they are sequenced.
• The value case is stated as: baseline 32 days, target 10 days, mechanism = rules-based determination replacing manual eligibility review plus front-loaded document completeness, owner = Benefits Operations Director.
• This is the answer pattern the exam rewards: outcome first, scope second, product third.