top of page
%20copy.png)
Search


We Had the Information — Just Not the Visibility
by: Jacqui Shemilt, 09 April 2026 The leadership team was frustrated. They had reports. They had documents. They had systems. What they didn’t have was visibility. They couldn’t be sure which document was the latest. They couldn’t find what they needed quickly. And they couldn’t trust that everyone was working from the same information. Critical knowledge lived across inboxes, folders, systems — and people’s heads. So every decision took longer than it should. Once the essent

Liah
Apr 91 min read


Sales closed the deal - and operations paid the price
by: Jacqui Shemilt, 12 March 2026 A client came to us frustrated. Orders were being assembled incorrectly. Deliveries were delayed. Customers were asking questions - and confidence was slipping. At first glance, it looked like an operations issue. But when we traced the problem back, the root cause was upstream. Sales were handing over deals with: • Missing specifications • Unclear product configurations • Assumptions instead of confirmed details • Critical information living

Liah
Mar 181 min read


3 Questions We Ask Before Any ERP or System Decision
by: Jacqui Shemilt, 03 March 2026 Before we ever talk about software, we ask three questions. Not about features. Not about vendors. Not about price. 1️⃣ Do you clearly understand how the work actually flows today? 2️⃣ Are decisions and handovers defined — or assumed? 3️⃣ Will this system simplify work, or just formalise the chaos? Most ERP and system failures aren’t technical failures. They’re process failures that get locked in by technology. At Bonacci Flow, we deliberatel

Liah
Mar 181 min read


Why This System Implementation Failed Before It Even Started
by: Jacqui Shemilt, 12 February 2026 On paper, the system was perfect. ✔ Right vendor ✔ Right features ✔ Right timeline But within weeks, frustration set in. Not because of the technology - but because no one had agreed on: • How work should flow • Who owned decisions • What ‘done’ actually meant The system didn’t fail. It simply automated confusion. Once we mapped the current state, the real issues surfaced - duplication, unclear handovers, invisible bottlenecks. Only then

Liah
Mar 171 min read


What mapping 47 admin steps taught me
by: Jacqui Shemilt, 03 February 2026 This started as a “simple” admin task. The kind everyone assumes should be quick. Once we mapped it end-to-end, it told a very different story - especially for leadership who only saw the start and end. 👉 47 steps 👉 Multiple handovers 👉 Repeated checks 👉 Workarounds layered over time The biggest issue wasn’t inefficiency. It was invisibility. No one had ever seen the whole process - so delays were blamed on people instead of the system

Liah
Mar 171 min read
bottom of page