<?xml version="1.0" encoding="UTF-8" ?><!-- generator=Zoho Sites --><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><atom:link href="https://www.stratocube.co.za/blogs/tag/best-practice/feed" rel="self" type="application/rss+xml"/><title>Stratocube Advisory Services - The Notebook, the Studio, and the Call That Came #Best Practice</title><description>Stratocube Advisory Services - The Notebook, the Studio, and the Call That Came #Best Practice</description><link>https://www.stratocube.co.za/blogs/tag/best-practice</link><lastBuildDate>Tue, 12 May 2026 12:01:30 -0700</lastBuildDate><generator>http://zoho.com/sites/</generator><item><title><![CDATA[The Notebook, the Studio, and the Call That Came]]></title><link>https://www.stratocube.co.za/blogs/post/there-s-a-hole-in-your-business-bucket2</link><description><![CDATA[A practical, team-based approach using data and structured problem-solving to remove waste, reduce defects, and fix root causes - not just symptoms. The result is better flow, higher quality, lower cost, and improvements that stick.]]></description><content:encoded><![CDATA[<div class="zpcontent-container blogpost-container "><div data-element-id="elm_CgXvI8wwSN20ma-uP-4OAA" data-element-type="section" class="zpsection "><style type="text/css"></style><div class="zpcontainer-fluid zpcontainer"><div data-element-id="elm_avscz6JbRpWPxnUBU23zKA" data-element-type="row" class="zprow zprow-container zpalign-items- zpjustify-content- " data-equal-column=""><style type="text/css"></style><div data-element-id="elm_F387LkPHRjGCRq576m6-eQ" data-element-type="column" class="zpelem-col zpcol-12 zpcol-md-12 zpcol-sm-12 zpalign-self- "><style type="text/css"></style><div data-element-id="elm_U_Nuc553SYSZI56FvIbq7g" data-element-type="heading" class="zpelement zpelem-heading "><style></style><h2
 class="zpheading zpheading-align-center zpheading-align-mobile-center zpheading-align-tablet-center " data-editor="true"><span><span>The Notebook, the Studio, and the Call That Came</span></span></h2></div>
<div data-element-id="elm_NNgkf_4-qMiRxRlrv8su3g" data-element-type="image" class="zpelement zpelem-image "><style> @media (min-width: 992px) { [data-element-id="elm_NNgkf_4-qMiRxRlrv8su3g"] .zpimage-container figure img { width: 800px ; height: 450.28px ; } } </style><div data-caption-color="" data-size-tablet="" data-size-mobile="" data-align="center" data-tablet-image-separate="false" data-mobile-image-separate="false" class="zpimage-container zpimage-align-center zpimage-tablet-align-center zpimage-mobile-align-center zpimage-size-large zpimage-tablet-fallback-fit zpimage-mobile-fallback-fit hb-lightbox " data-lightbox-options="
                type:fullscreen,
                theme:dark"><figure role="none" class="zpimage-data-ref"><span class="zpimage-anchor" role="link" tabindex="0" aria-label="Open Lightbox" style="cursor:pointer;"><picture><img class="zpimage zpimage-style-none zpimage-space-none " src="/Images/bespoke_tailor.jpeg" size="large" data-lightbox="true"/></picture></span></figure></div>
</div><div data-element-id="elm_s51f51H-T2e_w_jOhsVHGg" data-element-type="text" class="zpelement zpelem-text "><style></style><div class="zptext zptext-align-center zptext-align-mobile-center zptext-align-tablet-center " data-editor="true"><p></p><div><p style="text-align:left;">About nine months ago, back in mid 2025, I walked into a bespoke tailoring studio as a client, not as a management consultant. I was there because off-the-shelf clothing rarely fits me properly without requiring substantial alterations. But while the owner (let's just call him 'David' for purposes of this story), was taking my measurements, writing down my preferences, and capturing all the garment features and fabrics, I noticed something else.</p><p style="text-align:left;">The studio was beautiful, elegant, refined, and clearly fashioned with taste and care. But the process was not. Every measurement, every preference, every feature, and every detail was being captured by hand in a notebook. For a business offering that level of superior craftsmanship and style, the gap was obvious.</p><p style="text-align:left;"><br/></p><p style="text-align:left;">So at the end of our session, I suggested that a digital client management system would do more than modernise the process. It would protect information, create continuity, be more efficient, reduce risk, and make the business easier to scale. Also, using a tablet to capture all the client and garment information would just look more professional than jotting things down in a notebook. Notebooks are prone to being lost, having mugs of coffee knocked over them (<span style="font-style:italic;">been there and done that</span>), being lost or misplaced, and are also subject to other business risks.</p><p style="text-align:left;"><br/></p><p style="text-align:left;">David liked the idea, and said he'd actually been considering that recently, but he just did not know where to begin, tech wasn't his thing; high fashion and craftsmanship were. Because I believed in what he had been building over the years, I offered to do a small piece of research for him on a once-off <span style="font-style:italic;">pro bono</span> basis. A limited initial engagement. Enough to help him make an informed decision about how to proceed.</p><p style="text-align:left;"><br/></p><p style="text-align:left;">A few weeks later, I came back with a recommendation: Zoho CRM. It suited the business well. Better still, he was already using Zoho Books, so there was a natural fit. He was enthusiastic and decided to move forward with the recommendation. The business tried to move forward internally, but then the implementation stalled for various reasons.</p><p style="text-align:left;"><br/></p><p style="text-align:left;">Two weeks ago, David called me back. He could have called anyone, but he called me. That's the part that mattered. There is a lesson in that. Not because I had chased the work. Because when the need became real, he already knew whom he trusted.</p><p style="text-align:left;">That struck a resonant chord with me. It reinforced the principle that not every meaningful engagement begins with some fancy consulting pitch. Sometimes it just begins more simply, with being attentive, being fully present in the circumstance, offering a small piece of pro-bono value, and letting trust build over time.</p><p style="text-align:left;"><br/></p><p style="text-align:left;">Of course, that does not mean working for free indefinitely. It means a well-judged act of value appropriate to the circumstances can create the kind of trust that leads to a meaningful commercial engagement later.</p><p style="text-align:left;"><br/></p><p style="text-align:left;">I’m now helping the business implement the CRM and, in so doing, taking the business to 'the next level' operationally and strategically. An interaction with myself initially as the client, became a consulting conversation. A once-off pro-bono gesture later became a paid engagement.</p><p style="text-align:left;"><br/></p><p style="text-align:left;">Some of the best business development starts quietly, simply starting by noticing! The seed you plant in one conversation could finally have its moment, showing up later as bearing actual fruit! This story is not about the commercial win, it is about looking out for the opportunities to sow seed. Some seed falls on barren ground, and other seed falls on fertile ground. You have to be ready to lose some of the seeds sown in order to realise the multitude of fruit from the seeds that fell on fertile ground. Therein lies the moral and the lesson of this story!</p></div><p></p></div>
</div></div></div></div></div></div> ]]></content:encoded><pubDate>Sun, 26 Apr 2026 12:00:00 +0200</pubDate></item><item><title><![CDATA[There’s a Hole in Your Business Bucket]]></title><link>https://www.stratocube.co.za/blogs/post/there-s-a-hole-in-your-business-bucket</link><description><![CDATA[A practical, team-based approach using data and structured problem-solving to remove waste, reduce defects, and fix root causes - not just symptoms. The result is better flow, higher quality, lower cost, and improvements that stick.]]></description><content:encoded><![CDATA[<div class="zpcontent-container blogpost-container "><div data-element-id="elm_08-4pSUvTA6Q7Hn7mI0HXw" data-element-type="section" class="zpsection "><style type="text/css"></style><div class="zpcontainer-fluid zpcontainer"><div data-element-id="elm_4W72eHLpQyKddvDudG2kiA" data-element-type="row" class="zprow zprow-container zpalign-items- zpjustify-content- " data-equal-column=""><style type="text/css"></style><div data-element-id="elm_WTwaEb-1RMiG2CX-WayoAA" data-element-type="column" class="zpelem-col zpcol-12 zpcol-md-12 zpcol-sm-12 zpalign-self- "><style type="text/css"></style><div data-element-id="elm_2dXWrq5JTdCxDfFH7VuJgw" data-element-type="heading" class="zpelement zpelem-heading "><style></style><h2
 class="zpheading zpheading-align-center zpheading-align-mobile-center zpheading-align-tablet-center " data-editor="true"><span style="font-size:20px;"><b>&quot;Don't just tell me something’s wrong with the process, come up with a solution!&quot;</b></span></h2></div>
<div data-element-id="elm_XyWLicx9-LIdIel_7bwTWg" data-element-type="image" class="zpelement zpelem-image "><style> @media (min-width: 992px) { [data-element-id="elm_XyWLicx9-LIdIel_7bwTWg"] .zpimage-container figure img { width: 500px ; height: 286.53px ; } } </style><div data-caption-color="" data-size-tablet="" data-size-mobile="" data-align="center" data-tablet-image-separate="false" data-mobile-image-separate="false" class="zpimage-container zpimage-align-center zpimage-tablet-align-center zpimage-mobile-align-center zpimage-size-medium zpimage-tablet-fallback-fit zpimage-mobile-fallback-fit hb-lightbox " data-lightbox-options="
                type:fullscreen,
                theme:dark"><figure role="none" class="zpimage-data-ref"><span class="zpimage-anchor" role="link" tabindex="0" aria-label="Open Lightbox" style="cursor:pointer;"><picture><img class="zpimage zpimage-style-none zpimage-space-none " src="/Images/Hole%20in%20Bucket.jpg" size="medium" data-lightbox="true"/></picture></span></figure></div>
</div><div data-element-id="elm_OVl5EPYSS4eOI4llwssvwQ" data-element-type="text" class="zpelement zpelem-text "><style></style><div class="zptext zptext-align-center zptext-align-mobile-center zptext-align-tablet-center " data-editor="true"><p style="text-align:left;"><span style="text-align:justify;"><strong>Does this sound like a familiar refrain in your organisation?</strong> While it might seem like sound advice on the surface (</span><i style="text-align:justify;">a call for proactive thinking</i><span style="text-align:justify;">), leaders and managers who&nbsp;</span><strong style="text-align:justify;"><span style="font-weight:normal;">lean on this phrase too quickly can overlook real opportunities</span></strong><span style="text-align:justify;"> for process improvement, team development, and sustainable growth. In the world of business processes, problems aren't just hurdles; they're leaks in your bucket, draining efficiency, quality, and profitability.</span></p><div><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><strong>So What Then?</strong></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;">Enter <strong><span style="font-weight:normal;">LSS </span></strong><strong><span style="font-weight:normal;">(</span></strong><strong><span style="font-weight:normal;">Lean Six Sigma</span></strong><strong><span style="font-weight:normal;">),</span></strong><strong><span style="font-weight:normal;"> a practical, team-based method for improving processes by reducing waste and variation using data and structured problem-solving.</span></strong>&nbsp; <strong><span style="font-weight:normal;">Lean focuses on removing waste and improving flow. Six Sigma focuses on reducing variation and defects. LSS combines both by using</span></strong><strong><span style="font-weight:normal;">&nbsp;a disciplined approach to <strong>fix </strong></span></strong><strong>the right problem in the right way</strong><strong><span style="font-weight:normal;">.</span></strong></p><p style="text-align:justify;"><strong><span style="font-weight:normal;"><br/></span></strong></p><p style="text-align:justify;"><strong><span style="font-weight:normal;"><strong>People and Processes</strong></span></strong></p><p style="text-align:justify;"><strong><span style="font-weight:normal;"><strong><br/></strong></span></strong></p><p style="text-align:justify;"><span>Not all processes, or people, are created equal. Processes can vary wildly in complexity, from simple workflows to intricate systems intertwined with technology, people, and external factors. Similarly, individuals differ in their wiring: some excel at spotting issues but struggle with root cause analysis, while others thrive in data-driven environments but need guidance on creative problem solving or solution implementation. When a leader defaults to &quot;<i>come up with a solution</i>,&quot; they're assuming the person raising the problem has the full toolkit at their disposal to navigate from issue identification through to a viable fix: skills in data collection, &nbsp;<strong><span style="font-weight:normal;">analysis, solution design, and risk assessment</span></strong>. But that's rarely the case in any one individual, &nbsp;<strong><span style="font-weight:normal;">especially</span></strong> in dynamic, cross-functional teams.</span></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><strong>Knowing What We are Really Solving For!</strong></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><span>At a minimum, effective problem-solving in LSS requires accurately defining the problem, measuring performance with real in-situ data, analysing root causes, validating root causes, crafting improvements through targeted solutions, and then controlling outcomes for long-term stability (sustainability). This is the heart of the <strong><span style="font-weight:normal;">DMAIC framework</span></strong></span><strong><span style="font-weight:normal;">: </span></strong><strong><span style="font-weight:normal;">Define, Measure, Analyse, Improve, Control - a structured roadmap for solving process problems using data.</span></strong><span> It is a disciplined, data-backed structure that doesn't rely on guesswork or solo heroics. It's a lot to expect from any single employee without support to “<i>come up with the solution</i>”.</span></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><strong>A Quick Example</strong></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><span>Imagine a customer onboarding process that “feels slow.” A manager asks for a solution. The team suggests “add more staff.” But DMAIC would first define the exact start/end of onboarding, measure cycle time and rework, analyse where delays actually occur (handoffs, approvals, missing info, governance, etc.), improve with targeted fixes (clear inputs, fewer handoffs, standard work), and control the gains (checks, dashboards, ownership). <strong><span style="font-weight:normal;">Often, the outcome is faster onboarding with less effort</span></strong></span><strong><span style="font-weight:normal;">, </span></strong><strong><span style="font-weight:normal;">not more headcount (at greater expense).</span></strong></p><p style="text-align:justify;"><strong><span style="font-weight:normal;"><br/></span></strong></p><p style="text-align:justify;"><strong><span style="font-weight:normal;"><strong>The People Dynamics&nbsp;</strong></span></strong></p><p style="text-align:justify;"><strong><span style="font-weight:normal;"><br/></span></strong></p><p style="text-align:justify;"><span>LSS recognizes that some people thrive in solo analysis phases, others in collaborative brainstorming, and many benefit from a blend, often incorporating research or pilot testing and leveraging individual skills and experience within a team context.&nbsp;&nbsp;</span>By advocating &quot;<i>come up with a solution</i>,&quot; a leader's expectation hinges on unverified assumptions about the individual's skills, resources, and environment. It ignores development needs, team dynamics, and capabilities, and the coaching role inherent in modern management. Worse, it can lead to quick fixes that <span style="text-decoration-line:underline;">mask symptoms</span> rather than <span style="text-decoration-line:underline;">addressing root causes</span>, perpetuating 'Muda' (<strong><span style="font-weight:normal;">a Lean term for waste and non-value-adding work</span></strong>) and Variability (<strong><span style="font-weight:normal;">a major driver of defects and inconsistency</span></strong>). This&nbsp;<strong>pressure-to-fix-fast</strong> approach risks demotivating teams, eroding confidence, and missing chances to build a culture of continuous improvement, none of which fosters high-performing processes or engaged employees and teams.</p><p style="text-align:justify;"><br/></p><p style="text-align:justify;"><strong>World Class Thinking</strong></p><p style="text-align:justify;"><br/></p><p style="text-align:justify;"><span>Instead, embrace LSS as the best-practice antidote for impaired, inefficient, wasteful, unstable, and underperforming processes. It provides the discipline and structure to systematically plug and repair those holes in your business, supported by powerful tools&nbsp;<strong><span style="font-weight:normal;">when and where they are needed, for example: 5S (Sort, Set in order, Shine, Standardise, Sustain - a workplace-organisation method); or Value Stream Mapping (VSM) - a way to visualise end-to-end flow and identify delays and waste.</span></strong></span></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><strong>Opportunity Gateways</strong></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><span>When an employee flags a process issue, be it bottlenecks, defects, inefficiencies, or any other issue, view it as a gateway to the following opportunities (<strong><span style="font-weight:normal;">among others</span></strong>):</span></p><p style="text-align:justify;"><span><br/></span></p></div><blockquote style="margin:0px 0px 0px 40px;border:none;padding:0px;"><div><div style="text-align:justify;">1.&nbsp;<b>What do we truly understand about the problem's scope?</b> Using DMAIC's Define phase, map where it begins and ends, identify upstream/downstream interdependencies, quantify business impacts (e.g., cost of poor quality), assess effects on people, technologies, processes, and systems, and evaluate risks to governance, compliance, and customer satisfaction.&nbsp;&nbsp;<strong><span style="font-weight:normal;">Optional (when useful): SIPOC - Suppliers, Inputs, Process, Outputs, Customers - a high-level view of a process; and VOC - Voice of the Customer - what “good” looks like to the customer.</span></strong></div><div style="text-align:justify;">2.&nbsp;<b>Who should participate in problem definition and solution generation?</b> Involve stakeholders via &nbsp;<strong><span style="font-weight:normal;">RACI - Responsible, Accountable, Consulted, Informed - to clarify roles; or Kaizen - a continuous improvement workshop - to generate and test ideas quickly</span></strong> to strengthen interdepartmental relationships, tap subject matter experts, and ensure buy-in and collaboration for sustainable changes.</div><div style="text-align:justify;">3.&nbsp;<b>How can the team collectively learn by collaborating on this resolution?</b> LSS promotes cross-functional teams in the Analyse and Improve phases, enhancing organisational memory through knowledge management.</div><div style="text-align:justify;">4.&nbsp;<b>How can we boost our problem-solving capabilities?</b> Employ LSS techniques like <strong><span style="font-weight:normal;">CTQ (Critical to Quality): what must be true for the customer to be satisfied&nbsp;</span></strong>for prioritization, creative tools like brainstorming and other ideation techniques, and select the most fitting methods based on data and process type.</div><div style="text-align:justify;">5.&nbsp;<b>What low-cost, low-risk trials can test our hypotheses?</b> Use Improve phase pilots, such as <strong><span style="font-weight:normal;">PDSA - Plan, Do, Study, Act - a rapid test-and-learn cycle&nbsp;</span></strong>or small-scale experiments, to validate solutions without major investments.</div></div></blockquote><div><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><span>While this list isn't exhaustive, <b>it scales with the issue's complexity</b>. LSS isn't about temporarily fixing holes; it's about redesigning the bucket for durability. There’s no need to see Lean Six Sigma as a complex methodology that’s beyond your reach. Instead, view it as a clear, logical approach to problem-solving supported by the DMAIC framework, practical, powerful tools, and guided every step of the way by a knowledgeable LSS expert (whether in-house or external). They’ll lead you and your team through the DMAIC process in an approachable yet stimulating way, empowering everyone involved while delivering meaningful improvements to key business processes.</span></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><strong>Leader Perspectives</strong></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;">For leaders and managers, the shift is simple<strong><span style="font-weight:normal;">:</span></strong><span> don’t demand a fully formed solution upfront, <strong><span style="font-weight:normal;">sponsor a structured path to crafting a sustainable one.</span></strong> When someone raises a problem, try these three questions before jumping to fixes:</span></p><ol><ol><li style="text-align:justify;"><strong>What does “good” look like, and how will we measure it?</strong></li><li style="text-align:justify;"><strong>Where exactly in the process is the delay, defect, or rework happening?</strong></li><li style="text-align:justify;"><strong>What is the smallest safe test we can run to learn fast?</strong></li></ol></ol><p style="text-align:justify;margin-left:36pt;"><strong></strong></p><p style="text-align:justify;"><span><br/></span></p><p style="text-align:justify;"><span>Next time you hear &quot;<i>Don't just tell me what the problem is, come up with a solution!</i>&quot;, pivot to the wealth of opportunities LSS unlocks: individual learning through tool mastery, team learning via collaboration, leadership learning in project sponsorship, and organisational learning for sustainable process excellence! <strong><span style="font-weight:normal;">And importantly</span></strong></span><strong><span style="font-weight:normal;">, </span></strong><strong><span style="font-weight:normal;">better outcomes: faster flow, fewer defects, lower cost, and a calmer, more capable organisation.</span></strong></p></div></div>
</div><div data-element-id="elm_Mo6hX4GBawO27YYs_e6bfw" data-element-type="button" class="zpelement zpelem-button "><style></style><div class="zpbutton-container zpbutton-align-center zpbutton-align-mobile-center zpbutton-align-tablet-center"><style type="text/css"></style><a class="zpbutton-wrapper zpbutton zpbutton-type-primary zpbutton-size-md zpbutton-style-roundcorner " href="https://www.stratocube.co.za/contact?src=blog&amp;cta=post_bottom&amp;post=hole_in_bucket" title="Blog Contact Us Button" title="Blog Contact Us Button"><span class="zpbutton-content">Let's speak</span></a></div>
</div></div></div></div></div></div> ]]></content:encoded><pubDate>Thu, 08 Jan 2026 12:00:00 +0200</pubDate></item></channel></rss>