1 of 20

Collab 3.0��Streamlining team-to-team comms

2 of 20

Big goal: �to work seamlessly with partner teams, make the most of every opportunity and create continuity of care

3 of 20

As a reminder:

  • We won’t get it 100% right today!
  • We’ll need to try things and see how they work
  • Everyone is responsible for helping design.

4 of 20

The problem we’re trying to solve

5 of 20

The social contract

6 of 20

Outline of the solution we have available!

  • [add a screenshot]

7 of 20

Every solution creates new problems

8 of 20

Mmm, noodle soup!

Image credit: Allrecipes.com

9 of 20

Principles we’re proposing

Owner owns

Updater updates (which is everyone involved in that account)

Committed in our team

Strong social contract between teams

What could possibly go wrong?! 🤷‍♀️

10 of 20

Pre-mortem

11 of 20

Let’s pick three use cases

Use case 1

Use case 2

Use case 3

12 of 20

How will we make this work?

  • Different types of ‘accounts’
  • Minimum viable record!
  • Specific roles: owner and updater
  • Choosing and signposting owners
  • Journal entry categories and conventions
  • Housekeeping e.g. checking for existing record

13 of 20

What shall we agree to do as….

  • Owner
  • Updater

14 of 20

Beyond the database: how can we improve comms about partner projects and updates more generally?

15 of 20

Our own team contract

What are we promising to do?�

How will we hold each other accountable?�

16 of 20

Reviewing together

  • Who owns the whole database? (and what exactly is their role?)�
  • When will our review points be?�
  • How do we ensure the system evolves as our needs change?

17 of 20

Let’s try it out!

18 of 20

What would you need to make this happen?

19 of 20

  • Big thank you as always!
  • Here are next steps (e.g. kick off date, further training)
  • Suggested review points

Next steps

20 of 20

Let’s get started…