About ManagementPro
Most execution problems don’t start in execution. They start earlier — in the fuzzy front end, where outcomes are undefined and the logic connecting strategy to results was never made explicit.
ManagementPro was formed to close that gap. We work before planning begins, clarifying what an initiative must accomplish, what conditions it depends on, and whether the underlying logic will hold under real-world pressure. That clarity doesn’t slow things down. It makes everything that follows more reliable.
We are not a project management firm. We work in the space where most initiatives quietly lose their way — before schedules are built, before resources are committed, before the cost of unclear thinking becomes visible.
Not because teams work harder. But because the work finally makes sense. tives before execution begins—translating strategic intent into work teams can actually deliver.
Why Clients Call Us
They call when something important isn’t moving the way it should. Sometimes it’s a high-stakes initiative losing traction — not because the team is underperforming, but because the underlying design was never resolved. Everyone is executing. No one is sure they’re executing the right thing.
Sometimes it’s a strategy leadership has declared but can’t describe in terms of what must change, by when, and how they’ll know.
Sometimes it’s a decision still open, still blocking progress, because the real question underneath it was never clearly framed.
The presenting problem varies. The root cause is the same: design work that should have happened before execution began either didn’t, or didn’t go deep enough. ManagementPro is the call leaders make before the window closes.
What Makes This Different
Three things distinguish how we work.
We engage before direction hardens. The highest-leverage moment is before plans solidify and options close. Most consultants arrive after that moment. We work to be there before it.
Our work is testable. The LogFrame produces a cause-and-effect hypothesis — explicit outcomes, named assumptions, measurable results — that leaders can stress-test before committing resources.
The design holds. Initiatives built on explicit logic stay coherent under pressure. When conditions shift, there’s a principled basis for adjusting. The work doesn’t just start well. It holds.
Terry Schmidt
Terry Schmidt didn’t invent the Logical Framework. He was recruited to teach it. Then he modernized it.
In the late 1970s, the original developer of the LogFrame methodology sought someone to field-test and expand it across international development programs. Terry — an aerospace engineer who had moved into federal program management — was that person.
Over the next decade, he deployed and refined the methodology across 24 developing countries with USAID and the World Bank, in environments where assumptions broke constantly, alignment was fragile, and failure was expensive in ways that couldn’t be hidden.
What he recognized — and spent the next three decades proving — was that the same discipline making high-stakes development work succeed would work equally well in enterprise, government, and technology environments. His career since then has been that transfer.
His engineering background gave him the habit of systems thinking. His time in international development gave him tolerance for ambiguity and broken assumptions.
His MBA gave him the language of business. The combination is rare — and it shows in how he works.
He has trained more than 25,000 professionals through ManagementPro and through UCLA Extension’s Technical Management Program, where he has been an award-winning instructor for decades. His clients include Boeing, Microsoft, Sony, NASA, Los Alamos National Laboratory, the Department of Energy, and dozens of other organizations where getting it wrong is costly. He is the author of Strategic Project Management Made Simple and the forthcoming Designing for Execution.
Strategic Project Design — the discipline Terry built from the LogFrame — is described below.
Strategic Project Design
Strategic Project Design is not a planning methodology. It is the discipline that determines whether planning will work at all.
Most initiatives struggle not because execution is weak, but because the work was never fully designed. Teams move quickly from strategy to schedules. Timelines get built before outcomes are defined. Budgets get set before assumptions get tested. The result is a plan that looks complete but sits on logic no one has examined — and that gap fills with risk before the first milestone is missed.
Strategic Project Design works upstream of that. It clarifies the architecture of an initiative before planning begins: the outcomes it must produce, the conditions it depends on, and the causal chain connecting effort to results. That clarity doesn’t slow things down. It makes everything that follows — planning, resourcing, execution — faster and more reliable, because the decisions made early actually hold.
The tool at the center of the discipline is the Logical Framework (LogFrame). The LogFrame organizes an initiative across four levels — Goals, Purpose, Outcomes, and Inputs — and links them through explicit measures, verification methods, and assumptions. Used well, it functions as a testable hypothesis: if these inputs produce these outcomes, and these assumptions hold, the initiative achieves its purpose and advances the larger goal. Leaders can stress-test that logic before resources are committed, surfacing gaps and misalignment while they’re still inexpensive to fix.
Strategic Project Design precedes project management. It doesn’t replace it. Once the design logic is explicit, any planning approach — Agile, Waterfall, hybrid — works with it. The discipline isn’t a methodology to swap in. It’s the upstream work that makes the methodology you already use more reliable.