Function Analysis Workshop¶
Analytical workshop — instantiates Purpose Alignment Design
Takes one legacy role, routine, or artifact and asks what it actually does now — and whether that function still serves the purpose or has quietly become its own end.
Function Analysis Workshop takes one legacy role, routine, or artifact and asks a deceptively simple pair of questions: what does this actually do now, and does that function still serve the purpose? Its defining move is single-target functional decomposition — it strips a familiar activity down to the function it performs today (often not the function it was created for) and then draws the boundary between what still serves the purpose and what has quietly become its own end. It is a bottom-up dissection of one thing, not a portfolio-wide audit and not the design of anything new.
Example¶
A manufacturing plant runs a weekly hand-written shift-handover report that three supervisors spend two hours compiling. The workshop takes just this one artifact. First: what does it do now? Interviews and observation reveal the digital manufacturing-execution system already captures ninety percent of its content automatically, so the report's live functions are actually two: (a) a legal-feeling paper trail nobody has consulted in years, and (b) a ritual that makes the outgoing shift feel their work was witnessed. Second: do those functions serve the purpose — safe, informed shift transitions? The information function is obsolete duplication; the witnessing function is genuine but does not require two hours of transcription. The workshop draws the nonpurpose boundary: the report's information role no longer serves and can go, its social-acknowledgment role is worth preserving in a lighter form. The recommendation is to retire the written report and replace it with a five-minute verbal handover that keeps the witnessing without the overhead.
How it works¶
- Pick one target — a single role, routine, report, meeting, or policy.
- Elicit its current function empirically — what it actually does today, from the people who touch it, not from its founding charter.
- Separate stated purpose from live function — after years of drift these have usually diverged.
- Test each live function against the system's purpose.
- Draw the nonpurpose boundary — which functions still serve, which are obsolete or self-serving, and which are worth preserving in some other form.
Tuning parameters¶
- Target scope — narrow (one report) versus broad (an entire role). Narrow is decisive; broad blurs the analysis and invites hand-waving.
- Function granularity — how finely to decompose what the thing "does" before testing each piece.
- Empirical depth — asserting the function from memory versus observing or shadowing it. Observation surfaces hidden functions but costs time.
- Charitable-read setting — how hard to search for a hidden legitimate function before recommending retirement.
- Disposition bias — whether the workshop defaults to keep or to cut when evidence is ambiguous.
When it helps, and when it misleads¶
Its strength is surfacing the real, drifted function of a legacy activity and licensing honest retirement of what no longer serves. Its failure mode is cutting a function whose purpose you never actually understood — the trap Chesterton's fence warns against[n1]: a workshop that skips the empirical "what does it really do" step will mistake an invisible-but-load-bearing function for waste and remove it, only to discover what it was holding up. The classic misuse is running the workshop as cover to eliminate an inconvenient role that someone had already decided to cut. The guarding discipline is to require the charitable empirical read — prove you understand the fence's function before you take it down — and to keep the nonpurpose boundary anchored in observed evidence rather than assumption.
How it implements the components¶
means_purpose_map— traces the one activity's live functions to the purpose they claim to serve.misalignment_diagnosis— identifies where the live function has drifted from the stated one and why.nonpurpose_boundary— its signature: draws the explicit line between functions that still serve and those that have become their own end.
It dissects a single legacy function bottom-up. The portfolio-wide recurring audit run by a governance body is Mission Alignment Review, which carries the purpose_owner and purpose_drift_monitor this one-off workshop lacks; reconciling several teams' goals against a shared purpose is Goal Alignment Workshop, which holds a purpose_statement as its shared referent. It only recommends — it pulls no redesign_lever, because analyzing a function is not rebuilding it.
Related¶
- Instantiates: Purpose Alignment Design — the depth-first arm that tests a single legacy means against the purpose.
- Sibling mechanisms: Purpose-to-Metric Mapping · Mission Alignment Review · Outcome-Driven Design · Backcasting from Purpose · Goal Alignment Workshop · Product Purpose Review · Purpose-Clause Decision Record
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: A facilitated workshop lets participants jointly examine what a legacy role, routine, or artifact currently does and whether that function still serves its purpose.
Nearest alternative: Assessment, Review & Assurance — The session yields an evaluative conclusion, but shared participatory analysis rather than an independent audit is the operative form.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Management and process-improvement traditions analyze whether inherited routines still serve organizational purpose.
Related originating lineages:
- Engineering & Design — Value engineering and functional analysis independently examine what an artifact must do before redesign.
Review resolution: Both reviewers agree that organizational_management is primary: Management and process-improvement traditions analyze whether inherited routines still serve organizational purpose. I retain engineering_design only where the reviewers identify formative lineage, not every later application. I resolve origin_mode as cross_disciplinary_synthesis because the artifact joins distinct disciplinary contributions. I resolve domain_reach as multi_domain because it transfers across several fields but is not a domain-free primitive. Encyclopedia synthesis is true because the exact generalized packaging is an encyclopedia-authored combination or refinement.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Chesterton's fence — the principle that you should not remove a fence until you understand why it was put up. It is the exact caution a function analysis needs before retiring a legacy activity: identify the live function first, then decide. ↩