Organizational Design Reasoning Chain

validated business chain v1.0.0 cc-by-sa

Block ID: 29f61159-5d06-47b0-9845-c808f180c281

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.

Template

Reason through the organizational structure for the situation in {org_context}, since structure follows strategy and reorganizing without a strategic reason just churns people. (1) Start from what the organization must be good at to win — the capabilities the strategy demands — because structure should be designed to make those capabilities excellent, and copying another company's org chart imports their strategy's structure, not yours. (2) Identify the primary axis of organization the strategy implies: by function (deep expertise, efficiency), by product or business unit (speed, accountability, at the cost of duplication), by geography, or by customer segment — each optimizes something and sacrifices something, and pretending a structure has no tradeoffs is the core error. (3) Locate the critical interfaces: where must different groups coordinate closely, and does the proposed structure put those groups together or force them across a boundary? Most structural pain lives at the seams. (4) Assign clear accountability: for each key outcome, one owner with the authority to deliver it, since diffuse accountability is where structures fail. (5) Weigh the coordination cost of the structure against its focus benefit, and consider what mechanisms (roles, processes) can bridge the seams the structure creates. (6) State the recommended structure, what it optimizes and sacrifices, and the coordination risk to manage. Present the case for the alternative structure.

Reason through the organizational structure for the situation in {org_context}, since structure follows strategy and reorganizing without a strategic reason just churns people. (1) Start from what the organization must be good at to win — the capabilities the strategy demands — because structure should be designed to make those capabilities excellent, and copying another company's org chart imports their strategy's structure, not yours. (2) Identify the primary axis of organization the strategy implies: by function (deep expertise, efficiency), by product or business unit (speed, accountability, at the cost of duplication), by geography, or by customer segment — each optimizes something and sacrifices something, and pretending a structure has no tradeoffs is the core error. (3) Locate the critical interfaces: where must different groups coordinate closely, and does the proposed structure put those groups together or force them across a boundary? Most structural pain lives at the seams. (4) Assign clear accountability: for each key outcome, one owner with the authority to deliver it, since diffuse accountability is where structures fail. (5) Weigh the coordination cost of the structure against its focus benefit, and consider what mechanisms (roles, processes) can bridge the seams the structure creates. (6) State the recommended structure, what it optimizes and sacrifices, and the coordination risk to manage. Present the case for the alternative structure.

Variables

Name	Type	Required	Trust level
org_context		yes

org-designstructureoperating-modelchain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18