Build vs Optimize Decision Chain

validated business chain v1.0.0 cc-by-sa

Block ID: 3c258e6a-2a3f-4ece-a724-dc371cf51c53

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

Template

Decide whether the business in {growth_context} should invest in something new or optimize what exists, since both instincts — chase the new or polish the current — can be the wrong call. (1) Assess how much headroom remains in the current approach, because optimizing something near its ceiling yields diminishing returns while a fresh channel or product has room to run, and the reverse: abandoning an under-optimized asset with lots of headroom leaves easy value on the table. (2) Compare the marginal return on the next unit of effort: what a dollar or a week spent optimizing the existing engine returns versus the same spent building something new — this marginal comparison, not the absolute size, is the right basis. (3) Weight the certainty: optimization returns are usually more predictable and faster, while new bets are higher-variance and slower — so the right mix depends on the company's need for reliable near-term results versus its capacity to fund exploration. (4) Check whether the current approach is actually well-understood: if you haven't found its true ceiling, "we need something new" may be premature escape from an unfinished job. (5) Consider portfolio balance — starving all exploration to optimize today mortgages the future, while neglecting the proven engine for shiny bets starves the present. (6) State the recommendation, the marginal-return reasoning behind it, and the signal that would shift the balance.

Decide whether the business in {growth_context} should invest in something new or optimize what exists, since both instincts — chase the new or polish the current — can be the wrong call. (1) Assess how much headroom remains in the current approach, because optimizing something near its ceiling yields diminishing returns while a fresh channel or product has room to run, and the reverse: abandoning an under-optimized asset with lots of headroom leaves easy value on the table. (2) Compare the marginal return on the next unit of effort: what a dollar or a week spent optimizing the existing engine returns versus the same spent building something new — this marginal comparison, not the absolute size, is the right basis. (3) Weight the certainty: optimization returns are usually more predictable and faster, while new bets are higher-variance and slower — so the right mix depends on the company's need for reliable near-term results versus its capacity to fund exploration. (4) Check whether the current approach is actually well-understood: if you haven't found its true ceiling, "we need something new" may be premature escape from an unfinished job. (5) Consider portfolio balance — starving all exploration to optimize today mortgages the future, while neglecting the proven engine for shiny bets starves the present. (6) State the recommendation, the marginal-return reasoning behind it, and the signal that would shift the balance.

Variables

Name	Type	Required	Trust level
growth_context		yes

growth-strategyresource-allocationoptimizationchain-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