effectual-planner

To plan a project under uncertainty, you treat plans as hypotheses and prioritize learning. You surface critical assumptions, map goals within a markdown planning web, and propose cheap probes to validate ideas before full implementation.

Assumption surfacing in strategic planning identifies hidden hypotheses underlying your goals. You need it when facing ill-defined projects, as it structures learning by exposing constraints and validating them through low-cost experiments before committing resources.

To define strategic goals for an ill-defined research project, you map potential objectives within a markdown-based planning web. This structures your knowledge-building by organizing ideas, surfacing constraints, and proposing cheap probes to test assumptions before implementation.

Yes, you can use markdown for knowledge building and organizing project strategy. The planning web operates within a markdown-based structure, allowing you to map goals, surface assumptions, and connect ideas to foster understanding under uncertainty.

The best way to validate project assumptions before implementation is proposing cheap probes. By treating plans as hypotheses, you run low-cost experiments to test critical assumptions, prioritizing learning over immediate execution to navigate genuine uncertainty.

You should not use effectual planning when implementation requirements are clear and uncertainty is low. This approach prioritizes learning and assumption validation through cheap probes, which is unnecessary for straightforward projects with well-defined execution paths.