top of page

Deliver Data Projects in just Two Weeks with SPRINT

Producing results highly valued by business through a data project in just to weeks from a cold start sounds like a tough challenge, and it is. Though tough it is also achievable using a version of the SPRINT process invented by Google Ventures and a low code for data platform like Axellera Decision Data Central. Here is how.


Week one is all about getting a prototype that is best able to deliver your set goal and learning what needs to change and what is still missing to make it really great in production.

Preparing for the SPRINT

Preparation is key for a great SPRINT. Essential prep includes:

(1) picking the right participants including key data users, key domain experts and Data Analysts/Architects well matched to the topic, challenge and the other participants.

(2) picking a challenging topic and draft goal

(3) identifying ( and getting access to) any key data sources required

(4) an Axellera Decision Data Central environment ready for you to use in the workshop.

(5) getting a room you can use for the two weeks with white board space etc. and a sprint workshop kit. Read more about what's good room for SPRINTS + what should be in your SPRINT Workshop Kit here: and in the

MONDAY ( Week 1 )

Monday’s structured discussions and data collection activities create a path for the design sprint week.

In the morning, you’ll start at the end and agree to a long-term goal.

Next, you’ll make a map of the challenge. Then you ask the experts at your company to share what they know. Finally, you’ll pick a target: an ambitious but manageable piece of the problem that you can solve in one week.

In the afternoon you start on-boarding your key data for the challenge.

TUESDAY ( Week 1 )

In the morning, you’ll start with inspiration: a review of existing ideas to remix and improve and they key data resources you on-boarded on Monday. Then, each person will sketch out how the identified data can be best used to meet the goal following a four-step process that emphasizes critical thinking over artistry.

In the afternoon you will create some draft queries to provide answers to your questions using the data on-boarded on Monday. You’ll also begin planning Friday’s customer test by recruiting customers that fit your target profile.

WEDNESDAY ( Week 1 )

In the morning, you’ll start with critiquing the different approaches to getting answers to your challenge and review the draft queries you created to implement them with the data you on-boarded. As a result you will then decide which ones have the best chance of achieving your long-term goal.

In the afternoon you will add more flesh the winning approach. The main task is to storyboard the report(s) / dashboards(s) or other UX your target customers would need to unlock the value of data solution. You will also be identifying new data and queries you may need and take a note of any that need to change or can be dropped.

* The winning approach can be a composite of the ideas, approaches etc you reviewed.

THURSDAY ( Week 1 )

In the morning, you’ll start with triaging everything still missing for your storyboarded solution from wednesday. Sort into three categories:

(1) Must be in Fridays prototype with real data

(2) Must be in Fridays prototype but can be a wireframe sketch with a story you can show as part of the test/demo on friday. This should have a realistic chance of being completed in week 2

(3) Other stuff you can show as part of the future road map to users in Friday Week 1 and Week 2. You could categorise these further as

a. Coming Soon - this is what we will add in the coming months

b. Visionary Stuff - this may take a while but it's the directions we are planning/proposing to go over the next year or two. (usually these are things with wider dependencies)

You will then turn this into a plan for you as a team to deliver this protype throughout the rest of the day. The you will start delivering on that plan.

In the afternoon you will continue with delivering on that plan.

You’ll also make sure everything is ready for Friday’s test by confirming the schedule, reviewing the prototype, and writing an interview script

FRIDAY ( Week 1 )

In the morning, you’ll be interviewing customers and learn by watching them react to your prototype.

In the afternoon you will review the feedback and learning from the interviews. Then you will create a plan with everyting that will be needed for an Minimum Viable Product (MVP) version of your solution to demo to your target users / customers on Friday next week. The MVP should be something that is useful to your target users / customers. Complete enough to work from them but minimal enough for your team to deliver in the coming week.


Week one is all about taking the learning from week one about what needs to change and what is still missing to make it really great in production and translate it into a focussed plan of action to deliver a Minimum Viable Product (MVP) of your prototype. An MVP you can be proud of and which your target users will want to use asap.


In the morning, you’ll will work on delivering

In the afternoon you will start with a review of what you have working and what ist still missing and highlight any problems and blockers you may have discovered. Little demos can help a lot here. Adjust your plans for the remainder of the week if need. Also pick out the tasks your team needs to tackle in the rest of the afternoon and next morning.

Also during the week invite the people that should be in demo on Friday morning.

On Thursday Afternoon you should also script and rehearse the demo for Friday and prepare a script for any individual walk throughs with key users afterwards.

FRIDAY ( Week 2 )

In the morning, you’ll deliver the demo and if possible have individual walk throughs with key users to get further feedback and learn how best to roll out the MVP to them and keep them engaged and fired up through this process.

In the afternoon you will review the feedback and learning from the morning and sketch out a proposed roadmap for the MVP.

38 views0 comments
bottom of page