Define the system and unit of analysis
Specify process, population, product, time window, boundaries and aggregation level. Without a defined unit of analysis, measures and comparisons may represent different phenomena.
TECHNICAL GUIDE · STRUCKEL TOOLS
PRJ-01 · Projects
Complete Project Plan
Structures project governance from charter and scope through WBS, schedule, costs, quality, resources, risks, procurement and viability.
projeto · escopo · EAP · cronogramaFormulários Struckel
01
MANAGEMENT QUESTION
The problem the tool must make decidable.
Before opening a form, define the question that must be answered. A management tool is useful when it reduces ambiguity, exposes assumptions and makes clear which decision will be made from the evidence produced.
PRJ-01How can scope be decomposed and schedule, cost, quality, resources, risk and stakeholders governed consistently with expected project value?
Projects turn intention into deliverables under constraints of time, resources, scope and risk. Documentation should facilitate decisions and governance rather than merely record what happened afterwards.
Use it when there are deliverables, owners, dependencies, milestones, acceptance criteria or a need to track evolution objectively.
02
METHOD ARCHITECTURE
Technical construction: from operational definition to evidence.
A robust plan starts by defining the expected outcome and the starting condition. It then organizes actions, owners, deadlines, criteria and resources. Order matters: when action precedes diagnosis, the plan becomes a task list without a theory of results.
Define criteria before evaluation
Translate abstract concepts into operational definitions, scales, classification rules and data sources. Criteria should exist before the result to reduce retrospective interpretation.
Preserve traceability
Link each conclusion to data, observations, assumptions and owners. When a score is used, retain its components; when a hypothesis is used, record how it will be tested.
During review, look for actions without owners, dates disconnected from dependencies, costs without assumptions and goals without measures. A good plan lets you ask “how will we know it worked?” and find the answer in the document.
03
WORKED EXAMPLE
How the method behaves in a real situation.
For a B2B portal, the WBS separates authentication, catalog, orders, payments and migration. Each work package has acceptance criteria, estimate, dependency and risk; the schedule derives from the work rather than desired dates alone.
The example is intentionally specific. Numbers illustrate the reasoning and are not universal benchmarks: limits, scales and targets must be defined for the process being analyzed.04
MEASUREMENT AND INTERPRETATION
What to observe so the document does not become mere form filling.
Measures should serve reasoning. Whenever possible combine outcome, process and contextual evidence. For time series, look for patterns and variation rather than only point-in-time before/after comparisons.
01deliverables/WBS
02critical path
03cost baseline
04priority risks
05acceptance criteria
Consistency test
Ask whether another person, using the same definitions and evidence, would reach a similar interpretation. If the answer depends heavily on individual judgment, refine the operational definition, scale or data source.
05
LIMITATIONS AND GOVERNANCE
The tool supports decisions; it does not replace judgment, context and validation.
Established method/tool in professional and academic literature; exact implementation should be tailored to context.
A project plan is not a schedule. Without value, acceptance, risk and governance criteria, detailed dates can mask a poorly defined project.
Define an owner, review frequency, official data source and condition for reopening the decision. Link actions to deadlines and indicators, hypotheses to tests, and risks to treatment and follow-up.
DefinitionEvidenceInterpretationDecisionReview
06
METHODOLOGICAL BASIS
References for deeper study of the method.
The references below support the methodological family or principle used. Struckel’s digital implementation operationalizes application, documentation and traceability; it does not change the conceptual limits of the original sources.
PMI_PMBOK8
Open reference Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide). 8th ed. 2025.
PMI_WBS
Open reference Project Management Institute. Practice Standard for Work Breakdown Structures / PMBOK guidance on WBS and the 100 percent rule.
ISO31000
Open reference ISO 31000:2018. Risk management — Guidelines.
USE IT IN PRACTICE
Turn the method into a document ready for real work.
Struckel Forms offers a free way to structure this methodology with guided fields, contextual help and print/PDF preparation. Use the tool to organize reasoning; use consulting when the challenge requires design, implementation, facilitation or executive follow-up.