[{"data":1,"prerenderedAt":307},["ShallowReactive",2],{"pages:\u002Fresources\u002Ffaqs":3},{"id":4,"title":5,"body":6,"canonicalPath":279,"createdAt":280,"cta":281,"description":249,"extension":294,"meta":295,"navigation":290,"path":279,"schemaOrg":296,"seo":299,"slug":249,"status":303,"stem":304,"type":305,"updatedAt":280,"__hash__":306},"pages\u002Fresources\u002Ffaqs.md","FAQs",{"type":7,"value":8,"toc":248},"minimark",[9,14,18,23,26,31,34,37,41,44,47,51,54,57,61,64,68,71,74,78,81,84,87,91,94,97,100,104,107,110,114,117,121,124,127,130,134,137,140,144,147,151,154,157,161,164,167,170,173,177,180,183,186,189,193,196,199,202,206,209,212,215,219,222,226,229,232,235,239,242,245],[10,11,13],"h1",{"id":12},"strategic-project-design-logframe-faqs","Strategic Project Design & LogFrame FAQs",[15,16,17],"p",{},"Strategic Project Design helps teams test project logic before detailed planning and execution. These FAQs explain why projects fail, how project design differs from planning and project management, how the Logical Framework (LogFrame) works, and how AI can strengthen project design.",[19,20,22],"h2",{"id":21},"why-projects-fail","Why Projects Fail",[15,24,25],{},"These questions meet people at the problem level, before they know the language of Strategic Project Design or the LogFrame.",[27,28,30],"h3",{"id":29},"why-do-well-managed-projects-still-fail","Why do well-managed projects still fail?",[15,32,33],{},"Projects can be well managed and still fail because the underlying design logic is weak or unclear. Teams may hit deadlines, control costs, and complete the work, yet still miss the intended result. The problem is often the cause-and-effect logic connecting what the project does to what it is supposed to achieve.",[15,35,36],{},"Project management can execute a plan efficiently. It cannot correct flawed logic that was never tested. That is why the design should be challenged before major resources are committed.",[27,38,40],{"id":39},"how-can-project-risks-be-reduced-early","How can project risks be reduced early?",[15,42,43],{},"Project risks can be reduced early by examining the Assumptions built into the design. A project can be viewed through four connected levels of objectives, with Assumptions linking one level to the next. Making those Assumptions explicit quickly reveals where the logic may be vulnerable.",[15,45,46],{},"That provides a practical jumping-off point for deeper risk analysis: Which Assumptions are uncertain? Which matter most? What could cause them to fail? What should be changed, monitored, or managed before execution begins?",[27,48,50],{"id":49},"how-do-you-measure-project-success","How do you measure project success?",[15,52,53],{},"Project success should be measured against the results the project was designed to achieve, not simply whether tasks were completed on time and within budget. Define clear Measures or Indicators for each important objective and identify the evidence that will show whether it was achieved.",[15,55,56],{},"This shifts attention from activity to results. A useful test is: What would we need to see or measure to know that this project is actually working? Defining that evidence early makes success clearer, more objective, and easier to manage.",[19,58,60],{"id":59},"strategic-project-design","Strategic Project Design",[15,62,63],{},"These questions introduce the missing discipline between strategic intent and detailed planning and execution.",[27,65,67],{"id":66},"what-is-strategic-project-design","What is Strategic Project Design?",[15,69,70],{},"Strategic Project Design is a structured thinking process that turns strategic intent into a project that can be tested before detailed planning and execution begin. The Logical Framework, or LogFrame, is its primary methodology.",[15,72,73],{},"Strategic Project Design examines a project through four connected levels of objectives—Goal, Purpose, Outcomes, and Inputs—along with Measures that define success and Assumptions that connect the levels. By making the cause-and-effect logic visible and testable, it helps bridge the gap between strategy and execution before major resources are committed.",[27,75,77],{"id":76},"how-does-strategic-project-design-fit-with-project-management","How does Strategic Project Design fit with project management?",[15,79,80],{},"Strategic Project Design should be the front end of project management. It establishes what the project must achieve, why the proposed design should work, how success will be measured, and what Assumptions must hold before the team builds the detailed plan.",[15,82,83],{},"Once the design logic is sound, project planning determines how to get there—tasks, schedules, budgets, resources, and responsibilities—and project management drives and controls the work.",[15,85,86],{},"Design establishes what should work and why. Planning and project management determine how to deliver it.",[27,88,90],{"id":89},"what-should-be-established-before-detailed-project-planning-begins","What should be established before detailed project planning begins?",[15,92,93],{},"Before detailed planning begins, the team should be clear about what the project must accomplish, how success will be measured, what conditions must hold, and whether the cause-and-effect logic is sound.",[15,95,96],{},"That means clarifying the intended objectives, defining meaningful Measures, surfacing critical Assumptions, and testing whether each level can reasonably lead to the next.",[15,98,99],{},"Only then should the team move deeply into tasks, schedules, budgets, and resource assignments. Planning a weak design in greater detail only makes the wrong project more executable.",[27,101,103],{"id":102},"how-do-you-test-whether-a-project-design-is-sound","How do you test whether a project design is sound?",[15,105,106],{},"Test a project design by challenging each major cause-and-effect link and asking what must be true for that connection to hold. Examine the Assumptions, look for missing or insufficient results, and ask whether the Measures would provide convincing evidence of success.",[15,108,109],{},"Then test alternatives and failure scenarios. A sound design does not eliminate uncertainty. It makes the important logic, risks, Assumptions, and evidence visible enough to examine, challenge, and defend.",[19,111,113],{"id":112},"ai-project-design","AI + Project Design",[15,115,116],{},"These questions establish where AI adds value—and why understanding the underlying design logic still matters.",[27,118,120],{"id":119},"can-ai-create-a-logframe-or-project-design","Can AI create a LogFrame or project design?",[15,122,123],{},"AI can quickly draft a LogFrame, but producing one is not the same as designing a sound project. It can generate convincing objectives, Measures, and Assumptions while hiding weak logic beneath plausible but shallow AI output—what is increasingly called \"AI slop.\"",[15,125,126],{},"Understanding the LogFrame principles first helps you recognize those weaknesses and judge whether the design really holds. Then AI becomes far more valuable—challenging causal links, exposing hidden Assumptions, finding gaps, and suggesting stronger alternatives.",[15,128,129],{},"Knowing why the LogFrame works helps you put AI to work.",[27,131,133],{"id":132},"how-can-ai-stress-test-a-project-design","How can AI stress-test a project design?",[15,135,136],{},"AI can stress-test a project design by challenging the logic rather than merely expanding the plan. It can question whether the proposed results are sufficient, surface hidden Assumptions, identify missing stakeholders or results, challenge Measures, generate alternatives, and explore ways the design could fail.",[15,138,139],{},"AI can also compare competing approaches far faster than a team working manually. The goal is not to let AI make the decision. It is to use AI as a rigorous challenger that exposes weaknesses and stronger options before leaders commit significant resources.",[19,141,143],{"id":142},"the-logical-framework","The Logical Framework",[15,145,146],{},"These questions explain the primary methodology underneath Strategic Project Design—what it is, how it helps, how it is built, and where it came from.",[27,148,150],{"id":149},"what-is-a-logical-framework-or-logframe","What is a Logical Framework or LogFrame?",[15,152,153],{},"A Logical Framework, or LogFrame, is a one-page methodology for making a project's design logic visible and testable. It organizes four connected objective levels—Goal, Purpose, Outcomes, and Inputs—together with Measures and Assumptions.",[15,155,156],{},"The completed LogFrame shows what the project intends to accomplish, how success will be measured, what conditions the design depends on, and the cause-and-effect logic explaining why the proposed project should work.",[27,158,160],{"id":159},"how-does-a-logframe-help-design-a-project","How does a LogFrame help design a project?",[15,162,163],{},"The LogFrame helps design a project by forcing the team to answer Four Critical Strategic Questions:",[15,165,166],{},"What are we trying to accomplish—and why?\nHow will we measure success?\nWhat other conditions must exist?\nHow do we get there?",[15,168,169],{},"The first three are design questions. They clarify the intended results, evidence of success, and Assumptions required for the logic to work. The fourth is the planning question.",[15,171,172],{},"Answering the first three before diving into the fourth is what separates project design from project planning.",[27,174,176],{"id":175},"what-does-a-logframe-example-look-like","What does a LogFrame example look like?",[15,178,179],{},"Consider a project designed to improve new-employee performance:",[15,181,182],{},"Goal: Build a more capable and productive workforce.\nPurpose: New employees become productive faster.\nOutcomes: A redesigned onboarding program; manager guide; role-specific learning resources; progress-tracking system.\nInputs: Staff time, expertise, technology, and budget.",[15,184,185],{},"The design then tests whether those Outcomes, together with the necessary Assumptions, are sufficient to achieve the Purpose. Measures show whether the expected results actually occur.",[15,187,188],{},"One page makes the project's central cause-and-effect argument visible and testable.",[27,190,192],{"id":191},"how-do-you-create-and-use-a-logframe","How do you create and use a LogFrame?",[15,194,195],{},"Create a LogFrame by starting with the intended results and working backward through the logic. Define the Goal and the Purpose the project itself must achieve. Identify the Outcomes required to achieve that Purpose, then determine the Inputs needed to produce them. Add Measures and the important Assumptions behind each connection.",[15,197,198],{},"Then test the logic from the bottom up: Are the Inputs sufficient for the Outcomes? If the Outcomes are achieved and the critical Assumptions hold, will the Purpose follow?",[15,200,201],{},"Once agreed, the LogFrame becomes a compact reference for planning, alignment, risk review, measurement, and ongoing management.",[27,203,205],{"id":204},"where-did-the-logframe-come-from-and-who-developed-it","Where did the LogFrame come from, and who developed it?",[15,207,208],{},"The Logical Framework was developed in 1969 by Leon Rosenberg and colleagues at Practical Concepts Incorporated (PCI) for the U.S. Agency for International Development (USAID), responding to weaknesses in how projects were being designed and evaluated.",[15,210,211],{},"Terry Schmidt was later recruited by the original LogFrame development team, taught the methodology internationally, and helped extend its use beyond international development into business, government, technical, and project-management settings. ManagementPro's modernized approach retains the original causal logic while adapting its terminology and application to contemporary Strategic Project Design.",[15,213,214],{},"Background: PMI: Turning strategic goals into successful projects.",[19,216,218],{"id":217},"related-methods","Related Methods",[15,220,221],{},"These questions help readers connect the LogFrame to approaches they may already use.",[27,223,225],{"id":224},"can-a-logframe-be-used-with-agile","Can a LogFrame be used with Agile?",[15,227,228],{},"Yes. A LogFrame and Agile solve different but complementary problems. The LogFrame establishes the strategic design—the objectives, Measures, Assumptions, and cause-and-effect logic that define what the project must accomplish. Agile manages how the team develops, tests, learns, and adapts during delivery.",[15,230,231],{},"The LogFrame asks, \"Are we pursuing the right results?\" Agile asks, \"How can we build, test, and adapt effectively?\"",[15,233,234],{},"The delivery approach can evolve as the team learns while the underlying strategic intent remains clear and testable.",[27,236,238],{"id":237},"theory-of-change-vs-logframe-whats-the-difference","Theory of Change vs. LogFrame: What's the difference?",[15,240,241],{},"A Theory of Change and a LogFrame both examine how actions are expected to produce results, but they usually serve different purposes. A Theory of Change explores the broader pathway through which change may occur and is often expressed as a narrative or diagram.",[15,243,244],{},"A LogFrame turns a selected strategy into a more structured, testable project design with defined objective levels, Measures, and Assumptions.",[15,246,247],{},"A Theory of Change helps explore how change may happen. A LogFrame defines the project design that will be managed, measured, and tested.",{"title":249,"searchDepth":250,"depth":250,"links":251},"",2,[252,258,264,268,275],{"id":21,"depth":250,"text":22,"children":253},[254,256,257],{"id":29,"depth":255,"text":30},3,{"id":39,"depth":255,"text":40},{"id":49,"depth":255,"text":50},{"id":59,"depth":250,"text":60,"children":259},[260,261,262,263],{"id":66,"depth":255,"text":67},{"id":76,"depth":255,"text":77},{"id":89,"depth":255,"text":90},{"id":102,"depth":255,"text":103},{"id":112,"depth":250,"text":113,"children":265},[266,267],{"id":119,"depth":255,"text":120},{"id":132,"depth":255,"text":133},{"id":142,"depth":250,"text":143,"children":269},[270,271,272,273,274],{"id":149,"depth":255,"text":150},{"id":159,"depth":255,"text":160},{"id":175,"depth":255,"text":176},{"id":191,"depth":255,"text":192},{"id":204,"depth":255,"text":205},{"id":217,"depth":250,"text":218,"children":276},[277,278],{"id":224,"depth":255,"text":225},{"id":237,"depth":255,"text":238},"\u002Fresources\u002Ffaqs",null,{"title":282,"description":283,"links":284},"Ready?","The gap between strategy and execution doesn't close itself.",[285],{"label":286,"to":287,"target":288,"icon":289,"trailing":290,"size":291,"color":292,"variant":293},"Book a Discovery Call","calendly","_blank","i-lucide-arrow-right",true,"xl","primary","solid","md",{},{"primaryType":297,"jsonLdMode":298,"faqPage":290},"WebPage","generated",{"metaTitle":300,"metaDescription":301,"indexable":290,"robots":302,"title":5,"description":249},"FAQs | ManagementPro","Frequently asked questions about ManagementPro.","index,follow","published","resources\u002Ffaqs","page","c3k3vvBJdf1acmGnlB45xeOaoIxx05S14PW0z_f3AnI",1793666308082]