Training for Project Team

Starting a Business Design Sprint well prepared does not only apply to you as a coach. Also the project team should be well prepared, and if they are going to experience their first Business Design Sprint, make sure to give them the proper training beforehand.
Avatar of Karl Rabes

Karl Rabes

Business Design Coach

1. Purpose

The purpose of this preliminary training is to enable potential team members of Business Design projects to become a valuable member of a high performance Project Team. The goal is not only to teach them tools and methods but also to convey the experience and work attitude, as well as the mindset, we need and expect throughout a Business Design project. After the training, everyone should leave the room with a strong feeling of respect, anticipation and excitement about the upcoming project. They should know their individual Roles, the key steps in the Process and some specific Tools and Methods. They should have gained an understanding that Business Design projects are both demanding and manageable due to the fact that the entire process is highly structured, proven and supported by a professional Coach with many years of experience.

Sometimes it makes sense to not only invite potential team members of a Business Design project to the preliminary training, but also the sponsor(s). Especially when an organisation is taking it's first steps in Business Design, it is of great advantage if also the sponsor experienced a Business Design project first hand. In doing so, the regular Sponsor's Sneak Preview can be conducted efficiently and the sponsor knows, what kind of decisions are expected from his or her role.

Never start a Business Design project when the project teams members are NOT trained beforehand. It is almost impossible to guide  a team towards valuable output while training them on the methodology at the same time. A training is about learning and a project about output (for a sponsor and/or the organization). We train Project Teams to get ready for Business Design in our Academy. Join us for our next courses!

2. Duration

2 days

3. Participants

Max. 20 potential members of a Business Design project team

4. Preparation

  • Learning output defined with sponsor and/or HR department of the training

  • Agenda defined and aligned with sponsor and/or HR department of the training

  • All tools & materials prepared and printed

  • Case study prepared with Project Charter and some insights form a "fake" Discover phase

  • Participants invited, travels and accommodations arranged

  • Room & catering booked or organized

5. Tools & Materials

(for 20x participants)

6. Example Agenda

Day 1

Time

Activities

Format*

Stakeholders

08:30 - 09:00

Arrival and "Good Morning Coffee"

B

All

09:00 - 10:00

Welcome and introduction to Business Design

P

Trainer

10:00 - 10:15

Presentation of a case study including a Project Charter and some sample insights from a "fake" Discover phase

P

Trainer

10:15 - 10:30

Coffee break

B

All

10:30 - 11:00

Teamwork to get acquainted with case study materials

T

All

11:00 - 11:15

Deep dive: Design phase

P

Trainer

11:15 - 12:30

Ideation: Design of idea scenarios within the scope of the Project Charter

  • Definition of primary target groups

  • "Job(s) to Get Done" statements

  • Design of product and / or service scenarios (surprising > unbelievable > out of this world)

  • Consolidation to one scenario

T

All

12:30 - 13:30

Lunch break

B

All

13:30 - 15:30

Design of business models incl. consistency check

...optional: Briefing of prototyping engineers and designers

T

All

15:30 - 15:45

Coffee break

B

All

15:45 - 17:00

Visual storytelling with videos


T

All

17:00 - 17:30

Wrap-up

  • Today's (personal) highlights

  • Reflection of teamwork and learning output

  • Outlook 

D

Coach

Day 2

Time

Activities

Format*

Stakeholders

08:30 - 09:00

Arrival and "Good Morning Coffee"

B

All

09:00 - 09:30

Reflection of day 1 incl. "movie time" and reviewing the visuals / prototypes (may need more time here)

D

All

09:30 - 10:00

Deep-dive: Validate phase

P

Trainer

10:00 - 10:45

Collection of analogs & antilogs and definition of test focus (see Hypotheses & Experiments)

T

All

10:45  - 11:00

Coffee break

B

All

11:00 - 12:30

Derivation of questions (= exploration) and hypotheses (validation) incl. setup of experiments

T

All

12:30 - 13:30

Lunch break

B

All

13:30 - 15:00

Design of lean offerings / MVP

  • Functional requirements

  • Non-functional requirements

  • Scribbles / prototyping of key features

T

All

15:00 - 15:15

Coffee break

B

All

15:15 - 15:45

Add-on: Introduction to prototyping and/or field research with customers

P

All

15:45 - 16:45

Task management

T

All

16:45 - 17:00

Deep dive: Decide phase

P

All

17:00 - 17:30

Wrap-up and farewell

  • Today's (personal) highlights

  • Reflection of teamwork and learning output

  • Outlook

D

Coach

* P = Presentation | D = Discussion | B = Break | T = Teamwork