My first Anaplan project was a sh!t show.

This is what I have learnt during the years since so I avoid it ever happening again -

🔸 We dig deep on user requirements - spending quality time upfront understanding exactly what is required, relevant and reasonable within the project constraints of time, budget and quality goes a long way to ensuring we deliver exactly what is needed.

🔹 We design a robust data models upfront - a flexible, agile and responsive Anaplan data model is foundational to the design, development and deployment of its modelling logic. Time invested here ensures we have the necessary modelling structures to successfully design and build the calculation engines and eases the whole model build going forward.

🔸We communicate every day - open, transparent and honest communication between us and our client subject matter experts is crucial to avoiding bottlenecks, delays and rework. We are able to build rapport and trust so that ongoing project requests can be made and demands met in a more timely manner.

🔹We challenge assumptions - the way it has always been isnt how it should always be! If we believe a business processes, data management or modelling calculation just looks off then we will always raise them for discussion. Building on our developing rapport we work together to ensure the project is a success not just in terms of the modelling but also in the processes and data management.

🔸 Our core design philosophy is that simple always wins over complex - we seek out the simplest solution to all our modelling challenges. If we feel the first option smells like its too complex, more often then not there will be a simpler way. We seek it out! Always! Simplicity is a design choice and one we always strive to prioritise.

🔸We demo weekly - we walk through our work every week, without fail! It anchors us, keeps us accountable while ensuring we remain laser focused on delivering and demonstrating value from the start right through to the end. Also, we live by the fact that five days is often just the right amount of time to design and develop a sizable chunk of value. Therefore, we want to get it front of end users as soon as possible.

🔹 Model architecture - we adopt a sequential consolidation model design approach, building and consolidating local modelling before consolidating into a total group structure.

🔸We focus on one process at a time - we design and develop local modelling process one at a time plugging them into the group structure as we go.

🔹 We double down in the first stages - we strive to bank as much value as we can early in a project so we can draw down on any saved time when we inevitably come up against unexpected delays. This gives us space to breath, reassess and redirect if required.

Great model design must be a choice!