Just-In-Time Project Delivery

People don't believe when I tell them we deliver 6-month projects in 8 weeks. Here's how I structure Nolte to make it happen: 𝗪𝗲𝗲𝗸𝗹𝘆 𝗹𝗲𝗮𝗱𝗲𝗿𝘀𝗵𝗶𝗽 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲: We use Traction (EOS) to run everything. → Level 10 meetings focused on key metrics and issues → Scorecard tracking sales pipeline, revenue, and delivery indicators → One-on-ones with team leads to stay aligned 𝗧𝗲𝗮𝗺 𝘀𝗲𝘁𝘂𝗽: I don't manage engineers directly. Yanna Lopes leads all product and engineering as our head of product. She's accountable for: - Team performance and delivery - Quality metrics (we track bugs as percentage of total work) - Cross-functional alignment between design and development 𝗣𝗿𝗼𝗰𝗲𝘀𝘀 𝗺𝗲𝗲𝘁𝗶𝗻𝗴𝘀: → "Nolte Way" sessions focused on evolving our delivery methodology → Weekly metrics reviews on speed, quality, and predictability → Account-specific strategy sessions for complex clients -- The result from this strategy: → 1% bug rate across all projects → 85% of features ship within 6 days → Zero time wasted in traditional sprint planning Clear accountability and weekly alignment let us move fast without breaking things.

🚀 𝐉𝐮𝐬𝐭-𝐢𝐧-𝐭𝐢𝐦𝐞 𝐃𝐨𝐜𝐮𝐦𝐞𝐧𝐭 𝐑𝐞𝐥𝐞𝐚𝐬𝐞 Ever tried to swim upstream while carrying 10 bricks? That’s what happens when we flood a project with documents long before anyone needs them. 🔎 𝐓𝐡𝐞 𝐏𝐫𝐨𝐛𝐥𝐞𝐦 We’ve all seen it. Documents are released way too early, requirements are still shifting, drawings are not stable, and work instructions are written before the process exists. Everything gets approved… and then reality hits. Design updates roll in, suppliers push new constraints, and interfaces change. Suddenly, you’re revising released documents again and again, burning change numbers and confusing everyone. Tip: Release documents just in time, when the downstream user actually needs them. Not earlier, not later. ✨ 𝐖𝐡𝐲 “𝐉𝐮𝐬𝐭-𝐢𝐧-𝐓𝐢𝐦𝐞” 𝐑𝐞𝐥𝐞𝐚𝐬𝐞 𝐌𝐚𝐭𝐭𝐞𝐫𝐬 - Minimises waste: less time spent maintaining outdated docs. - Increases agility: documentation evolves with the product, not ahead of it. - Reduces risk: fewer chances that someone uses the “wrong” version. - Improves clarity & accountability: every release is a conscious, traceable event. 🛠️ 𝐇𝐨𝐰 𝐭𝐨 𝐝𝐨 “𝐉𝐮𝐬𝐭-𝐢𝐧-𝐓𝐢𝐦𝐞” 𝐃𝐨𝐜𝐮𝐦𝐞𝐧𝐭 𝐑𝐞𝐥𝐞𝐚𝐬𝐞  1️⃣ Define release gates up front. In your CM plan, identify phases or triggers that justify a formal release, e.g., after the requirements freeze, module design sign-off, before procurement, pre-production, etc. CM2 promotes a dataset-based release approach rather than all-at-once or whenever you feel like it. 2️⃣ Release when downstream users need it. If procurement needs a long-lead item, release its documentation even if the full BOM isn’t ready. And yes, CM allows that. 3️⃣ Use a formal release mechanism with revision control. Every released document gets an identifier, a date, and a baseline reference, making it traceable. Once released, changes are controlled via a closed-loop change process. 4️⃣ Treat docs like parts: no “stockpiling.” Just as modern manufacturing embraces lean or Just-In-Time manufacturing to avoid excess inventory and waste, apply that lean logic to documentation, too. Only release what you need, when you need it. 5️⃣ Synchronize with actual workflows and avoid “fake readiness.” If documentation is released too early, teams may act on outdated or placeholder info. If released too late, it creates bottlenecks and risks rework. Use configuration-status accounting to track what’s released and what’s still draft. 🧩 𝐂𝐨𝐧𝐜𝐥𝐮𝐬𝐢𝐨𝐧 In a robust configuration management program, formal release isn’t a “one-and-done” event; it’s a rhythm. As the project matures, documents flow through baselines, but only when they are “needed and stable,” a CM2 Just-in-Time mindset. 🔁 So let’s drop the  “ready-all-docs-early” and “release-all-at-once” approaches and move to “release-on-demand.” #CM2 #ConfigurationManagement #PLM #ProductLifecycleManagement #Engineering #DocumentManagement #JustInTime #Lean #CM

Just-in-time requires more planning, not less. It's easy to think of planning as about telling others what to do - and dead wrong, planning is about... well, making plans. Planning is making sure the organisation is ready to respond to customer demand without creating chaos in the process. #Yearly planning sets the horizon. Imagine you’re running a factory. Once a year, you sit down with your team and ask: what new products are we introducing? What will customers expect from us next year? Do we need to invest in new machines, new lines, or new skills to make these products? These are big bets. For instance, if we plan to launch a new electric vehicle, we might need a battery plant. If we want to double output, we might need a new paint shop. Yearly planning is about committing resources to create the capacity to produce what we want to sell tomorrow. Then comes #quarterly planning, where we get closer to reality. Here, we ask: how many cars do we need to build in the next three months to meet customer orders? Do we have enough people, parts, and support staff to keep production flowing? It’s also where we look at the whole system: do we have enough logistics support, maintenance technicians, trainers, to handle that volume smoothly? Quarterly planning aligns the organisation to make sure the volume can be achieved without putting people or machines at risk. #Monthly planning is where the rubber meets the road. The aim here is stability. Production works best when the pace is steady. Big fluctuations create waste everywhere. So each month, planners look at what was consumed last month, adjust for any changes in customer demand, and plan week by week to keep production as stable as possible. They also start planning for mix – which products to build in which sequence – to match what is actually selling. Finally, the plant receives a #daily production plan. That’s what teams see on the shop floor. It tells them: today, this is what we’re building. It’s the result of yearly bets, quarterly alignments, and monthly adjustments, turned into daily work to serve customers reliably while learning how to do it better every day. Yes, plans are worthless, so we need to be flexible - but planning is everything because flexibility is not chaos and we need to create stable conditions to be flexible. #LeanIsAwesome

Today’s construction projects increasingly operate more like supply networks than traditional jobsites. Materials arrive just in time and are often modular. Storage space is limited. Sequencing decisions ripple across the entire schedule. The projects that perform best recognize this reality early. They integrate disciplined, creative thinking around supply chain control into project delivery from day one, coordinating material procurement, delivery windows, and installation sequencing as a single system. This approach consistently reduces schedule risk and improves overall project performance. Winning in construction in 2026 will require more than building expertise. It will require advanced logistics discipline, supply chain awareness, and teams that understand how movement and timing drive results. #ConstructionLeadership #SupplyChainManagement #ProjectDelivery #LogisticsStrategy #FutureOfConstruction