01 / Why (Start With the Why, Not a Blame Game): Projects do not slip by magic. When a build stalls, the first step is stepping back to ask two plain questions: Why did the business invest in this in the first place, and why have things not gone smoothly? No finger‑pointing and no methodology lectures. Once everyone is honest about where the friction actually sits, we can work it out and move forward.
02 / What (Design for Business‑to‑Person (B2P), Not Just to De‑Risk the Business): Early in my career, I was told my work looked "too B2C and should be more B2B" (Business‑to‑Consumer rather than Business‑to‑Business), right up until the iPhone launched and people realised B2P is key. Our audience are always people. We need to contextualise content for the human doing the job, not just tick a box to de‑risk the business.
03 / How (Map Real Capacity, Not a Neat Waterfall Gantt Chart): Not all stakeholders are as available as originally anticipated, and in the real world work rarely flows in a neat waterfall Gantt chart. Whether I am brought in for hands‑on instructional design and development or to rescue a wider programme, the fix is practical: Establish clear roles and responsibilities, find out who actually has capacity, collaborate properly, and agree a realistic plan that hits project deadlines.
Have a training build that is stuck? Book a 48‑Hour Tactical Triage at TacticalLearning.co.uk.