Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Previous quarter: [insert link to previous quarter]


This section links to the OKRs tracked in Tability 2.0

[link to Tability OKRs plan]

Related projects

Use this section to link to the projects active during the quarter. You’re free to use your tool of choice, but it should be easy for anyone to find out the specs/details of the things being worked on.


The section below should be filled at the end of the quarter by the key stakeholders. Ideally the entire team can contribute, but if too big (10+ people) I would suggest having key representatives instead (or better, the big team should be split into smaller ones with their own plan).


List all the people that are present for the retrospective.

Objectives grading

For each of the Objectives (not the KRs) listed in Tability, we write down a simple assessment of where we ended up.

The example below is an excerpt from /wiki/spaces/PD/pages/1981284353.




Get 2.0 in the hands of customers


  • (plus) Our team is using the V2

  • (plus) Got great feedback on onboarding → “Have had a chance to play with the app, one of the most intuitive experiences for building out a plan that I have used.”

  • (minus) Got distracted by unplanned project that started after the quarter.

  • (minus) Only our team is using V2

  • (minus) Still at alpha level, missing a lot of core features

Become a trusted source for goal-setting and OKRs


  • (plus) ODT is launched

  • (plus) Good SEO, owning the ‘Outcome Driven Teams’ search term

  • (plus) Started to build relationships with writers.

  • (minus) Having trouble getting consistent flow of content

  • (minus) Need to ramp up onboarding of new contributors

  • (minus) 0 podcasts published - need to find easier process for this

Looking back

Use the Looking back section to think about what happened during the quarter. This will help everyone to bring back the start of the quarter in mind and get the right context to think about the future.

  • What are key events that might have affected the work? (holidays, new hires, unforeseen event, key launches…)

  • What are good things that happened?

  • What are bad things that happened?

How to:

  • Nominate 1 writer for the key events and take 2-3 mins to list all the things that happened during the quarter.

  • Open up the docs to all contributors and take another 5 mins to list all the good things and bad things that happened during the quarter.

  • Don’t try to come up with solutions! This section is purely about sharing information – no judgement. You’ll have an opportunity to discuss options in the next section.

You’ll find below some examples taken from /wiki/spaces/PD/pages/1981284353. Replace with your own evaluation.

  • Key events

    • Person xxx joined the team

    • Big holiday rotation from Thanksgiving to Christmas to NYE (end November → end December)

    • Launched project xxx mid-October

    • [write any key event]…

  • Good

    • Remote team working well in autonomous fashion

    • Learned a lot on the ambassadors / referral program

    • Customer Stories! (blue star)

  • Bad

    • Bit off way more than we can chew

    • Too many big projects = taking too long to get things in the hands of people (ODT, V2, stories, etc)

    • Need to automate more of the tedious tasks – too much time spent on manual stuff

Going forward

Here you can start listing ideas on how you can improve next quarter:

  • What should we start doing?

  • What should we stop doing?

  • What should we continue?

How to:

  • Each contributor takes 5-10 mins to list their suggestions in the start/stop/continue columns.

  • Do not discuss the suggestions! This is a brainstorming exercise and it’ll be extremely costly if you stop to argue each statement.

  • Once everybody is done (or 10 mins have passed) you can read all the suggestions and:

    • Clarify things if they’re ambiguous (don’t judge, just clarify what is meant)

    • Group items that are similar

  • When the grouping is done, you can vote on start and stop items! Each contributor has 3 (star) that they can add next to the item they value.

  • When the voting is done, you can take 5 minutes per item to discuss the top 3.

You’ll find below some examples taken from /wiki/spaces/PD/pages/1981284353. Replace with your own evaluation.




  • Sharing experiments in Slack with team

  • Implementing and tracking a simple content strategy (star)(star)

    • (ex: 2 posts per week, 1 twitter, 1 linkedin, etc….)

    • Reusing past blog posts as content on socials

    • Improving social and ODT workflows (and automation) so we can be more consistent

    • Share knowledge more

  • Implement and track a simple positive feedback strategy

  • Ship smaller things every week across all disciplines (star)

    • Experiments

    • Features

    • Social assets

  • Direct sales (star)(star)

  • Automate all the things again(star)

    • Onboarding drip feed

    • Sales contact

  • Show our customers that we’re active and alive!

    • Post on Slack Community every day, as a team

  • More Product Design

    • Increase collaboration between dev and design

  • Thinking about our success in converted users, not just users(star)(star)

  • Hiding V2

  • Big projects - break things into smaller tickets (Ship more!)(star)

  • Weekly ritual (goals review → demos)

  • Writing down interviews and chat with customers/partners

  • Iterating on the product, V2 is needs to be great

  • Having fun, bring delight to product and social through our brand voice

What’s next? Planning the next quarter!

  1. Create a new plan in Tability 2.0.

  2. Create a new quarter plan in Confluence.

  • No labels