Tips to Improve Project Methodology

I've managed $500M+ in projects over the years. The successful ones were all built around the same 10 principles: Give me 3 min, and I'll show you how you can lead your next project with confidence. 1️⃣ Start with Why Most project managers think they’re paid to produce deliverables. That’s bogus. Every project exists to create value. What’s the driving reason behind yours? Dig deeper than the first answer. Your project's purpose becomes a compass for decisions—and a powerful narrative to align and motivate your team. 2️⃣ Define “Conditions of Satisfaction” If your client, architect, and field team aren’t aligned on the definition of done, you’ll never truly finish. Before diving into details, clarify what you’re building and how success will be measured. Get expectations on paper. Show sketches. Build mockups. Whatever it takes. Your goal: never have the “Wait—I thought we were doing XYZ” conversation. 3️⃣ Know the Constraints Every project is defined by five levers: • Time • Scope • Budget • Quality • Value Only one (maybe two) truly matter to the client. Know what you’re optimizing for so you can make smart tradeoffs. 4️⃣ Get the Right People Your project will never be better than the people on it. You don’t need warm bodies. You need the right people in the right roles. Build your team around functions, not names. Set expectations early. Give feedback often. 5️⃣ Big Goals, Small Steps Break your project into major deliverables—then smaller chunks. Boulders -> Rocks -> Pebbles -> Sand Use tools like product breakdowns, sketches, and process flows. 6️⃣ Build a Real Timeline Every construction job has key milestones. Use pull planning, Takt, & LPS to lay out each step with realistic durations. Validate your plan with your team. Then—and only then—negotiate. 7️⃣ Risk Management Something WILL go wrong. Build a Risk Register early. Review it weekly. Rank risks by impact × likelihood. Use the TAME framework: - Transfer - Accept - Mitigate - Eliminate Antifragile projects absorb shocks. Fragile ones shatter. 8️⃣ Dealing With Change A single change won't hurt you. 100 will. Standardize how changes are submitted, evaluated, approved, and communicated. Track every change in a central log and communicate it widely. 9️⃣ Tools & Processes Your tools exist to do 3 things: - Communicate - Coordinate - Document Don’t chase shiny features. Choose tools your team will actually use. Then build repeatable processes around approvals, onboarding, access, etc. 🔟 Stakeholder Communication Most projects fall apart because of miscommunication. Map your key stakeholders. Spend 80% of your time on the 20% who can make or break your job. Tailor how and when you communicate to meet their needs. - - - - - 📌 P.S. Interested in project leadership? Join 7,500+ construction pros who read The Influential Project Manager—a free weekly newsletter with 1 idea to lead people and predict outcomes. Every Tuesday.

Ever been thrilled to kick off a new coaching or facilitation project, only to have things unravel before your eyes? You’ve got the green light, your client’s excited, you’re excited... and then: 😬 Deliverables turn into moving targets. 🫨 Tasks start sneaking into the scope. 🙄 Communication becomes reactive. 🙄 And somehow, you're doing more than you signed up for. Sound familiar? These issues can lead to frustrated clients, strained relationships, and results that don’t reflect your expertise. Worse, you’re left questioning your own abilities. The root cause? Poorly initiated projects. The fix? A rock-solid kickoff meeting. Here’s how I run mine to set the stage for smooth sailing: 1️⃣ Set the agenda and introduce the team. Share the agenda in advance so everyone’s prepared. A quick intro sets a collaborative tone. 2️⃣ Review the project overview. Revisit the high-level goals and objectives. Frame it as a partnership—you’re in this together. 3️⃣ Explore hopes and fears. Ask what success looks like for the client, but also what could go wrong. Addressing fears early helps build trust. 4️⃣ Create a risk and opportunity register. Most people track risks, but don’t stop there. Highlight opportunities to amplify success—maybe another internal initiative aligns with your work. 5️⃣ Revisit the timeline. Pull the timeline from your proposal and check if it still works. Revise as needed and confirm key milestones. 6️⃣ Discuss team culture and expectations. How do you want to work together? Align on communication styles and ways of working to avoid surprises later. 7️⃣ Define next steps. End with clarity: What happens next, and who’s responsible for what? 💡 Pro tip: Send pre-work in advance, like a draft risk/opportunity register. The meeting should refine, not start from scratch. The result? ✅ Clarity ✅ Alignment ✅ stronger relationships. A well-run kickoff leads to happy clients, repeat business, and—you guessed it—referrals. Start strong, finish stronger. ~~ ✍️ What’s one thing you always include in your project kickoff? Let me know in the comments! 👇

You ran the sessions. You found the themes. The insights feel right. But before you present, a quiet question lingers, did I go deep enough? Did I check the right things? This is the part of qualitative UX research we don’t always emphasize. Not just doing the work with care, but supporting it with structure. Adding rigor isn’t about questioning your effort - it’s about strengthening your insights. It brings clarity, consistency, and confidence - for you, your team, and anyone who’ll act on what you’ve found. Here are eight practical ways to add that kind of rigor without slowing your work down. Start with triangulation. Don’t rely on just one type of data. Pair interviews with usability testing, behavior logs, or survey responses. Ask another researcher to take notes independently and compare interpretations. This builds confidence that your insights reflect more than one lens. Maintain an audit trail. Keep a record of key decisions, theme changes, or shifts in scope. Use a shared doc, spreadsheet, or even versioned codebooks. Others should be able to see how your findings evolved- not just the end product. Practice reflexivity. Before analysis, write down what you expect to find. During synthesis, notice when your background might be influencing what feels important. If you’re working in a team, make this a shared habit. You’re part of the instrument, and that’s worth tracking. Use member checking. Once your findings are drafted, send a summary to a few participants and ask if it reflects their experience. Their feedback will tell you where you’ve nailed it- and where you need to dig deeper. Use structured frameworks. Lincoln and Guba’s trustworthiness criteria are great for longer studies. The PARRQA checklist helps keep fast-paced projects grounded. Either way, frameworks give your work consistency and make your choices visible. Look for negative cases. Instead of just confirming patterns, search for outliers. Find the participant who doesn’t fit the theme. Revising your analysis to include their story makes your findings more durable. Make your insights transferable. Don’t stop at “users want X.” Add who those users were, what tools they used, and what constraints they faced. When findings are rich in context, teams can apply them more confidently. Document key decisions as they happen. Use a shared log or notes thread. Track sampling shifts, analysis changes, design pivots. Later, include this in your final report. It shows how you got from raw data to real insight- and helps others trust it. Rigor isn’t about adding more work - it’s about adding more strength. Even a few thoughtful checks, built into your workflow, can make your qualitative UX research clearer, more credible, and easier to stand behind when the pressure’s on.

Projects don’t fail at the end. They bleed out quietly. The dashboard’s green. Scope is locked. Risk register: pristine. But deep down, something’s off. And then: collapse. These five failure patterns operate quietly beneath traditional project governance. Most project managers don’t see them coming. Most executives don’t know to look for them. Let’s change that. 1️⃣ 𝗧𝗵𝗲 𝗛𝗶𝗱𝗱𝗲𝗻 𝗖𝗮𝘀𝗰𝗮𝗱𝗲 𝗘𝗳𝗳𝗲𝗰𝘁 One change order doesn’t seem dangerous. Until it quietly shifts timelines and inflates costs by 20 to 40 percent. You’re not managing a project. You’re managing a web of invisible triggers. ✅ Fix: Map interdependencies, not just deliverables. One change? Check every downstream impact before approval. 2️⃣ 𝗗𝗲𝗰𝗶𝘀𝗶𝗼𝗻-𝗠𝗮𝗸𝗶𝗻𝗴 𝗙𝗿𝗶𝗰𝘁𝗶𝗼𝗻 𝗟𝗼𝘀𝘀 When decision-makers sit too far from execution, delays go unspoken. By the time leaders hear about a problem, the team has already worked around it three times. ✅ Fix: Flatten the information flow. Real-time visibility beats formal escalation. Informal standups uncover truth faster than formal updates. 3️⃣ 𝗧𝗵𝗲 𝗠𝗲𝗮𝘀𝘂𝗿𝗲𝗺𝗲𝗻𝘁 𝗕𝗹𝗶𝗻𝗱 𝗦𝗽𝗼𝘁 You can’t manage what you don’t measure. Many teams launch without clear performance thresholds, bias checks, or value realization metrics. ✅ Fix: Define success at the start—not after go-live. Measure more than delivery. Measure adoption, behavior change, and realized business value. 4️⃣ 𝗧𝗿𝗲𝗮𝘁𝗶𝗻𝗴 𝗖𝗵𝗮𝗻𝗴𝗲 𝗟𝗶𝗸𝗲 𝗟𝗼𝗴𝗶𝘀𝘁𝗶𝗰𝘀 You explain the “what” clearly. But the “why” never lands. Employees nod in meetings, then quietly work around the new process. ✅ Fix: Change isn’t just about communication. It’s about emotion. Give people space to grieve the old way before pushing the new one. Trust builds adoption. 5️⃣ 𝗧𝗵𝗲 𝗨𝗻𝗶𝗾𝘂𝗲𝗻𝗲𝘀𝘀 𝗕𝗶𝗮𝘀 “This project is different.” It’s probably not. When leaders skip reference class analysis, they ignore past patterns (and repeat them). ✅ Fix: Study three similar initiatives. Understand where they struggled. Use real data to inform planning, not assumptions. These aren’t isolated issues. They all stem from a shared root cause: We manage projects like delivery machines, while ignoring the people, the relationships, and the blind spots that actually drive success or failure. You can hit every milestone and still miss the outcome. ----- 👋 I’m Lars – delivering transformation that sticks. 🔔 Follow me for more on fractional leadership and change management.

90% of projects fail because of mental blind spots. Senior Program Management is a game of systems, not speed. If you’re focused on a 'To-Do' list, you’ve hit your ceiling. 8 frameworks to stay ahead: 1. The Cynefin Check Categorize the environment first. Management styles that work for clear tasks fail in chaotic ones. Match your approach to the domain. 2. Pareto Analysis (80/20) Audit your friction. A small group of stakeholders or a specific technical debt usually generates most of the noise. Focus your energy there. 3. The Pre-Mortem Imagine the project collapsed six months from now. Trace the specific risks that caused it. Address those "hidden" killers while you still have lead time. 4. Second-Order Thinking Evaluate decisions by their downstream effects. Every "quick fix" carries a future cost. Ask: "And then what happens?" 5. Parkinson’s Law Work expands to fill the time you give it. Tighten internal milestones to flush out unknowns earlier in the cycle. 6. The O’Toole Effect People clear easy emails to avoid high-friction tasks. Move the "hardest rock" before your first meeting. 7. Cost of Delay (CoD) Translate time into dollars. Quantify exactly what is lost for every week a milestone is missed. It turns a schedule debate into a business decision. 8. The Bus Factor If a project stops because one lead is unavailable, you have a single point of failure. Cross-train the team. Move knowledge into shared systems. Which one is your team missing? Drop a comment below. 👇

Regulators blame it for quality failures.   Firms rely on it for profitability.   Yet almost no firm trains their auditors in it.    Project management is one of the key drivers of a successful audit. Efficiency and profitability often hinge on how well the audit is project managed. And weak project management is commonly cited by regulators as a root cause of audit quality failures found in inspections. I recall when I was first in charge of audits, I got overwhelmed. Trying to organize what each team member was supposed to be doing each day was a big challenge. Keeping people busy and the audit on track was a lot, on top of my own workload. Then, when I was promoted to managing a portfolio of audits, that problem scaled. I had to be on top of several audits and a much bigger team. Looking back, it wasn’t just a problem of experience. It was because I was never given the tools or environment to be in control.  To implement stronger project management, you’ll be more successful if you have three core capabilities: 1. Workflow Visibility: get your arms around all the tasks to be performed. Your methodology dictates the tasks. And your prepared-by-client list identifies the information you need from others. 2. Work in Sprints: timebox your work into shorter cycles with defined progress review points. Weekly sprints work well. And at the end of the week conduct a formal debrief to learn and improve quicker. 3. Control Scope: when scope and deadlines move, plan before you commit. Log the change, size it up, and decide how best to resource it.     There is no shortage of Project Management models to choose from. But for all the hours of training I received in the Big 4, not one was on project management! Here are 10 models to choose from. Pick one, train your people, and start using stronger project management!  1) Scrumlite  2) Kanban  3) Scrumban  4) Critical Path Method (CPM)  5) Critical Chain Project Management (CCPM)  6) Timeboxing  7) Rolling Wave Planning  8) StageGate Lite  9) DrumBufferRope (Theory of Constraints)  10) Earned Value Lite (EVMlite)    And as a bonus!  Two prioritization models:  1) MoSCoW Prioritization  2) Eat the Frog    This is a clear and obvious win. Investing in project management will bring a huge return in both efficiency and quality. And it will deliver a better audit experience for your team and your clients! Which of these models do you think would make the biggest difference in audit fieldwork? And why?   

✅How to create the most effective WBS for your project: 1. Follow the 100% Rule. The WBS should include 100% of the work required for the project, covering every deliverable, task, and activity. It should not include work that falls outside the project’s scope (i.e., nothing left out, and nothing added). 2. Create Hierarchical Levels. A well-structured WBS has a clear hierarchy that divides the project into increasingly detailed components. The general structure usually has three to four levels: - Level 1: The overall project (the highest-level deliverable or outcome). - Level 2: Major phases or deliverables of the project (e.g., design, implementation, testing, deployment). - Level 3: Sub-deliverables, tasks, or work packages that make up each phase. - Level 4: Further breakdown of smaller tasks or activities, depending on the complexity. 3. Use Clear and Descriptive Naming. Each WBS element should be described in a way that clearly communicates what work is to be done. Avoid vague or generic terms. Use action verbs and nouns that describe specific deliverables and outcomes. 4. Ensure the WBS is Measurable. Each task or work package should be measurable, meaning you can track its progress, completion, or results. This ensures accountability and allows you to monitor the project effectively. 5. Focus on Deliverables, Not Activities. The WBS should emphasize (deliverables) rather than activities. For example, instead of breaking down a task like "Write code," describe the deliverable, such as "Develop software module for feature X." 6. Level of Detail Based on Project Size. The level of detail in your WBS should be appropriate for the complexity of your project. Large, complex projects may require more detailed breakdowns, while simpler projects can have fewer levels. Ensure that the WBS is detailed enough to assign clear responsibilities, yet not overly complex to avoid confusion. 7. Ensure Clear Dependencies. The WBS should outline the dependencies between tasks. This helps in scheduling and resource allocation, and ensures that the project flows logically from one phase to the next. 8. Create Work Packages. At the lowest level of the WBS, break down the project into "work packages" — the smallest units of work that can be easily assigned, scheduled, and tracked. Work packages should have clearly defined start and end points, costs, and responsible team members. 9. Use a Consistent Numbering System. Assign unique identifiers or numbers to each level and component in the WBS (e.g., 1.0 for the main project, 1.1 for a sub-deliverable, 1.1.1 for a work package). This makes it easy to reference tasks in reports and communication. 10. Incorporate Feedback and Adjustments. A WBS should not be static. As the project progresses, or if there are changes in scope, the WBS should be updated. Review it regularly with your team to ensure that it still reflects the project’s current scope and objectives.

High-Quality Project Management Templates & Documents: https://lnkd.in/dCGqF98z Writing a Strong Project Plan Changes Everything Great results rarely happen by accident. Studies show nearly 70% of initiatives struggle due to weak planning, not execution. When direction is clear, teams move faster, costs stay controlled, and confidence grows across stakeholders. The difference between chaos and control usually starts with how well the plan is written. 🎯 Start With Outcome Thinking Before writing tasks, define the final picture. Research shows teams with outcome-defined planning achieve 2.5x higher success rates. Write what success looks like in measurable terms. Not “improve performance,” but “reduce processing time by 20%.” Precision removes confusion and builds trust instantly. 🧠 Write For Humans, Not Documents Most plans fail because they are written like legal files. People follow simple, visual, and structured thinking. Use short sections, clear flows, and logical sequencing. Organizations using simplified planning structures report 35% faster decision cycles. 📊 Turn Assumptions Into Visible Risks Hidden risks destroy timelines. High-performing teams document assumptions openly. Data shows projects with assumption tracking reduce rework by up to 30%. Write assumptions beside each major deliverable. If something changes, impact becomes visible immediately. ⏱ Plan Backward From Deadlines Instead of building forward, start from the final delivery date and move backward. This method improves schedule reliability by nearly 28% in large transformation initiatives. Reverse planning exposes hidden dependencies early. 🔗 Connect Tasks To Business Value Every task must answer one question: Why does this exist? Plans aligned with business outcomes show 40% higher stakeholder approval rates. When value is clear, funding, support, and momentum increase automatically. 📁 Document Decisions, Not Just Activities Execution teams struggle when decisions are not captured. Writing decision logic improves transition from planning to execution by 50%. Always capture why choices were made, not only what was chosen. 🤖 Blend Data, Experience, And Pattern Recognition Modern planning mixes historical data, predictive insights, and human judgment. Organizations using data-supported planning improve forecast accuracy by 35% and reduce budget overruns significantly. 🚀 The Real Secret Strong planning is not about documents. It is about thinking discipline. Clear thinking creates clear execution. Clear execution creates predictable results. If you want ready-to-use frameworks trusted by professionals worldwide, explore: High-Quality Project Management Templates & Documents: https://lnkd.in/dCGqF98z #ProjectPlanning #BusinessTransformation #PlanningStrategy #OperationalExcellence #PMO #DeliverySuccess Disclaimer: Sometimes images may contain some errors in designing process, so please focus on content of this post and ignore the design errors.

If I were starting a new PROJECT today and wanted to plan it with ZERO prior knowledge, I'd do this: Step 1: Define Your Objective • Clearly articulate what success looks like for the project. • Break down the high-level goal into smaller, manageable milestones. • Ensure the objective aligns with stakeholders' expectations to avoid misalignment later. Step 2: Build Your Plan Backwards and Leverage Historical Data Most people skip this step entirely. But this is a huge mistake—because you risk creating a plan that doesn’t align with deadlines, resources, or realistic expectations. Here’s how: • Start from the final deliverable and work backward to define the timeline. • Gather and review historical data or similar project examples to understand typical timelines and challenges. • Identify key dependencies and create a logical sequence for tasks. • Use project planning tools (like Gantt charts or Kanban boards) to visualize your plan. • Clearly define roles and responsibilities for each stage. Pro tip: Don’t forget to account for buffer time—projects rarely go 100% as planned. Step 3: Identify Risks and Create a Mitigation Plan This isn't easy. But if you can do this, you will get: • Clarity on potential roadblocks before they derail progress. • Stakeholder confidence in your ability to deliver. • A proactive, problem-solving mindset that boosts your credibility. Here's a quick way to do this: List out possible risks, evaluate their impact and likelihood, and create a plan to minimize or respond to them. Collaborate with your team to spot any blind spots. Don't skip this step. It took me months of trial and error (and some chaos) to crystallize these steps—hope this helps! 🚀

30 60 90 Day Plans can be a very useful and simple method to drive specific process improvement projects or initiatives I generally use them to plan out specific projects and goals within an overall Continuous Improvement (CI) approach. 💠 I start with identifying a specific issue, and then breaking down the plan into three phases- 30 days, 60 days and 90 days. That's all kept very high-level, as in the visual below. 💠 The first 30 days are usually focused on learning and planning, the next 30 days are focused on implementation and monitoring and the final 30 days are focused on evaluation and optimization. The whole approach is kept in line with Lean Six Sigma thinking: PDSA- Plan Do Study Act and DMAIC- Define, Measure, Analyze, Improve, Control. 💠 Beyond the high-level plan, it's important to get into the nitty gritty details of improvement. This involves setting specific milestones for the end of each of the 30 day periods and agreeing roles and responsibilities with each team member. 💠 It is REALLY important to have systems and processes that support scheduled check-ins. If you are using cycle planning, the team must agree how they will communicate and collaborate. It may be a mixture of daily huddles, weekly team meetings, 1:1's or something else. 💠 It helps to use simple project management tools (e.g. Trello, Asana, or Microsoft Project) to visualize progress and manage tasks. Just make sure that support is high if people are unfamiliar with the technology as technology could be barrier otherwise! 💠 I like to keep it simple and at the end of each 30-day period, review the progress made towards the milestones. Discuss what worked well and what didn’t, and use these insights to improve the next phase. 💠 Remember to recognize all efforts and celebrate the achievements at each milestone. 💠 And when it comes to evaluation, conduct a thorough review of the entire initiative at the end of 90 days. Assess the outcomes against the original objectives. Gather feedback from the team on the process and outcomes to inform future projects. 💠 Really importantly, build in a continuous improvement approach to your process management. Establish a routine of regular feedback, monitoring, and adaptation to continually improve the process. Have you any experience with cycle planning? Have you any tips for people? Leave your thoughts in the comments 🙏 #changemanagement #strategicplanning #goals #continuousimprovement #cycleplanning #projectmanagement