[email protected] | +44 (0) 131 564 0562
MasterDistiller

The Third Door Part 3: Don’t Boil the Ocean

The Structured Implementation Approach


(Please note: This is a fictional story, inspired by the real-world journeys, successes and pain points of our MasterDistiller clients and peers. Any characters, events, or specific figures are illustratively based on these only.)


Glen Auld had decided to move forward. Decision made, vendor engaged, kick-off call scheduled. Isla, as managing director, had agreed the investment with a clear ROI laid out. The fragmented cask records, regular compliance scramble, board pack assembly from five disparate sources, these were problems across the whole business, and her position going into the kick-off was straightforward: get the whole operation onto the new system and stop managing around tools that were no longer fit for purpose.

The AI opportunity “art of the possible” outlined in the weeks prior had its foundations in clean, connectable data across the context of the whole operation. The sooner the whole system was live, the sooner that foundation existed to be leveraged. Read more about the AI opportunity in our previous post:

Isla’s thinking was reasonable. The data structure had already been mapped. The decision already made. Why stage something when the groundwork was already laid and the business case already clear? The capability was there, the resource available in the team, and the vendor ready to start.

The MasterDistiller implementation team had heard this before. Not because it was a naive request, it was often the instinct of most leaders who had committed to a transformation to get it executed, see the full benefit and move on to the next challenge in the business’ growth. The phased response was not a case for a longer engagement. It was a practical explanation of why a phased approach would get Glen Auld to a better outcome faster than doing everything at once.


The case for a phased implementation is not just about managing disruption, resource or limiting risk – though it can do all of these. It can be about the structural compounding advantages that each completed phase creates for the one that follows.

The Data Structure Is Already in Place

Phase 1 forces the distillery to clean, structure, and validate its data The conventions are established, the formats agreed, the migration process tested and proven. When Phase 2 begins, that foundation and framework already exists. Data for the next area loads into a structure that the business already understands and agrees on, not a new one being defined under pressure.

General Configurations Are Already In

The core system settings established in Phase 1 – user permissions, approval workflows, integrations with accounting software, the chart of accounts, the site and warehouse structure – carry across every subsequent phase. Phase 2 is not starting from scratch. It is extending a working foundation. The configuration work that represents the most technically intensive part of any implementation is done once, not repeated.

Staff Are Already Familiar with the System

By the time future phases begin, the team has been using the system in real time and with practical day to day use cases, the good, the bad and the ugly of their typical workload. They know the interface, how to navigate records, run reports, and flag exceptions. They know what the small tweaks they want to make are to bring outsized gains from using it. Phase 2 training focuses on tweaking and refining to get the most out of the investment, on creating new workflows, not on teaching people how the system works. The learning curve that consumes the most energy in a comprehensive go-live is already behind them and the speed of learning is compounded by actual use.

The result is that each phase is genuinely faster and less disruptive than the one before it. Phase 1 carries the heaviest lifting. Phase 2 and Phase 3 build on a platform that is already stable, already understood, and already trusted by the team using it.


Regardless of whether it’s a wholesale setup or even of which part of the operation is being implemented first, the methodology follows the same structure. The starting point is usually the area causing the most acute operational pain – the process that costs the most time, carries the most risk, or is capable of generating the most outsized returns.

  1. Data Gathering: Existing data is mapped, audited, and structured ready for migration. Or if making a change then the data structure and framework is discussed, reviewed, adjusted, challenged, tested and then signed off before re-working of existing data. This is where the fragmentation surfaces – spreadsheets in different formats, records with gaps, conventions nobody documented or workflows reliant on inconsistent mapping. It can be the most time-consuming part of any implementation the part most commonly underestimated and also one of the most valuable, alongside training, to really spend the time on. Doing it properly can be the difference between a clean go-live and one that spends its first weeks correcting data and redoing workflows.
  2. System Configuration & Data Load: The platform gets configured to reflect how the distillery actually operates, not the other way round! Cask classifications, production workflows, charts of accounts, user permissions, operation types, logistics routings, re-order and stock rules and much more. Once configuration is agreed and signed off, the cleaned data can be loaded into this framework. This work happens while the business continues to run on existing systems. The team is not disrupted while these critical foundations are built.
  3. Training: Training is delivered in stages, focused on the workflows the team actually needs from day one. The MasterDistiller team deliver interactive tailored sessions and testing environments equipping staff with curated knowledge for their roles, tools to go and get stuck in, try things, and break things if that’s what it takes. The test system provides means that no permanent changes are made to real data, while also producing a realistic environment to work in. Modern training methods, tools and platforms allow staff easy access to materials in a variety of formats to meet them where they learn their best. Targeted training on a system the team has already seen configured for their own processes, with their own data, lands differently from any generic product walkthrough and surfaces any further insights or requirements that help accelerate the business’ growth.
  4. UAT – User Acceptance Testing: Before go-live, the team tests the system against their actual processes. Real scenarios, real data, real workflows – not a theoretical checklist. UAT is the moment the distillery confirms the system is good to go. Problems are fixed before go-live. A thorough UAT process is the single most reliable way to avoid the post-launch firefighting that undermines confidence in new systems.

Isla’s initial instinct – get everything done at once, see the full return on the investment as quickly as possible and get started on the next project – was not wrong as a business goal. That goal remained the same, but there was more than one approach to achieving it. The board could see more, sooner, from a Phase 1 that went live cleanly and proved its value, allowing more business momentum and input behind the remaining project.

Cask management, warehousing, and inventory became Isla’s Phase 1. The largest asset value and driver, highest-pain area in terms of data capture and structure and the one that had produced the Board questions she couldn’t answer quickly. With the longest history of consuming disproportionate and unnecessary reporting time across the finance and production teams.

The Data Gathering stage was where the cask record fragmentation finally got resolved. Forty-three entries with missing or unverifiable data, traced back to source records, corrected, documented and workflows amended.

When Phase 1 went live, Callum in his role as Distillery Manager, ran the cask inventory report that had previously required cross-referencing three files. It took seconds. Finance Director Sarah’s compliance submission that had consumed two days ran from one connected system in minutes. The sales team knew exactly what casks they had for sale, and which bottlings were planned, with allocations and depletions coming in the next phase. The Board question Isla had taken three days to answer after the previous quarterly review took five minutes at the next one and her monthly ABL Bank Reporting was suddenly the click of a saved favourite report button. The visibility and transparency for the whole business was amplified and the compounding gains on speed and accuracy of decision-making off the back of it helped start the acceleration of the business.

Phase 2 started straight after. Callum’s team already knew the interface. The bottling module training took a fraction of the time. The data structure from Phase 1 meant the bottling records loaded cleanly into an already-proven foundation, with available live cask data from last week’s production to test – data they knew, data they trusted, data that they’d input into the system themselves.

Isla’s instinct to move fast was right of course. The phasing was actually the unlock that made the speed possible.


A staged single-phase implementation – Data Gathering, System Configuration and Data Load, Training, UAT – does not slow things down. Each completed phase leaves the data structure in place, the core configurations done, and a team already familiar with the system. Every subsequent phase is faster, shows returns quicker, and is less disruptive than the one before it.

MasterDistiller has migrated clients over from all major legacy platforms as well as modern platforms, and of course Excel.

Start with the highest-return area. Get it right. The rest follows from a foundation that is already stable, already trusted, and ready for acceleration.



Request a Quick Quote or Book a Demo

Get Started with MasterDistiller

Pricing from only £350

Sebastian Navarro

Request a Quick Quote

Contact us to discuss your upcoming project, request a quick quote or for more information on MasterDistiller or Odoo.

Book a Demo

Book a demo with a member of our team to explore the features available with MasterDistiller and Odoo. Demos typically take approximately an hour but can be tailored to your requirements.