Practical writing on programs and project portfolios: business cases, prioritization and steering. Translated from our German blog.
Projects fizzle out because reporting never becomes a habit. What helps is an owner who knows what they're signing up for, fixed reviews and consequences.
Other departments work on a cross-functional program when clear numbers per department keep the room for hoping small and are consistently followed up.
Read moreYou defend your program budget in a cost-cutting round by putting a number on what a cut costs in revenue and showing yourself where your program can be cut.
Read moreConvince the CFO despite uncertain numbers with the one assumption that carries the case, a set amount to test it and a clear recommendation.
Read moreCut innovation reporting overhead by automating the copy-paste between tools, gates and slides first, then by getting by with one or two gates.
Read moreBesides skills shortages and costs, three in-house hurdles slow innovation in German companies: heavy business cases, incomparable numbers, no follow-up.
Read moreInnovation programs rarely fail because of culture. Five patterns repeat, from false clarity in planning to vanity metrics in execution.
Read moreScoring models look like math but are gut feeling in disguise. A better way to evaluate innovation projects: one metric (NPV), ranges and Monte Carlo.
Read morePortfolio prioritization rarely fails because of the formula. It fails because of the information gap between business units and decision-makers.
Read moreIn a due diligence, consultants check hundreds of assumptions, but only three to five decide the purchase. Ranges and sensitivity analysis show you which.
Read moreThe AI says “3 to 5 percent” and you type 4 into the cell. That's where the business case breaks, because the range is the answer, not a step toward the number.
Read moreIn a short conversation we take one of your initiatives and show how an idea becomes a business case with targets and tracking.