Big Book of WOW Articles

Scaling Team Design

The problem is with scale comes complexity A team of one is the most efficient team to get data work done, but only if that one person is an expert in every step of that data work and has enough time to complete all...

Information Products

Concept of an Information ProductAn Information Product is an approach to describe a subset of data, analytical and visualisation requirements in a way that the business stakeholders can agree what they will get and...

Team Design Patterns

Common Design Patterns There are several common patterns for defining organisational and team design structures. Functional Design, where the structure is based around specific functions, such as marketing, finance, or...

Skills vs Roles

It is a silo problem When we structure our teams based on roles not skills we strike a bunch of problems that are related to the anti-patterns roles seem to invoke. Team members will perform the data tasks to be done...

Concept of Prioritisation

Multitasking is the problem, we should focus on one thing at a time Data teams should only work on one thing at a time, but the problem is they often don’t know what the most important thing is. Stakeholders know the...

Core Prioritisation Patterns

Eisenhower Matrix The Eisenhower Matrix, also known as the Urgency-Importance Matrix, is a simple two-by-two matrix that helps prioritise work based on their urgency and importance. Work is divided into four...

Fixed Mindset Prioritisation Patterns

There are a number of popular fixed mindset prioritisation patterns. MoSCow The Moscow prioritisation pattern is often used to prioritise tasks, features, or requirements in software development. The pattern consists...

AgileData prioritisation patterns

There are a number of prioritisation patterns we have found in the agile and product domains which we have proven are useful when used to prioritise work in the data domain. We use the Information Product Canvas and...