Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

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



Related projects

Children Display



Complete the seed round

titleon track


Did a good job of securing $1M for the round


But still have to finalize the legal + accounting work


Money not there yet, but should be by end of January


(plus) $1M AUD secured


(minus) Round not closed yet



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.

Children Display



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

titleoff track


Work on the round took time away from coding the V2

  • (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.”


However, given that the focus of the quarter was to get V2 out, this is a pretty sad outcome for this goal.


On the plus side, the internal team has fully migrated to the V2


(plus) Team is using the V2


(plus) Positive feedback on onboarding


  • (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


titleoff track
  • Haven’t built the beautiful experience that was originally planned.

  • The idea was to build it on top of V2, and V2 itself got delayed

  • Did some manual emailing, but without a dedicated person it will be hard to have an impact

  • Suggestion: go back to automated drip feed, in a similar way to HelpScout

  • (plus) Outlined the onboarding flow

  • (minus) Manual process is costly

  • (minus) Customers still left to be successful by themselves


titleOff Track


Overall, potentially the wrong objective for just one quarter - will likely take a lot longer to be fully ‘low-touch’


Part way there for doubling leads but in a high-touch way



4 reviews added to public review sites - not enough to meet goal, but the process for requesting reviews seems to be promising and simple


Long lead time for recruiting & onboarding ambassadors/advocates but well on our way to having our first few


5 experiments recorded and another 3 experiments in progress currently

  • In hindsight, some attempted tests weren’t recorded

  • Idea: Slack channel for growth/experiment recording

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


(plus) ODT Launched


(plus) Good SEO


(minus) Couldn’t get enough external posts


(minus) Podcasts not started

Looking back

Key events


Maisy starts with Tability in October


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)

    • First user on V2

    • Launched ODT

    • Seed round started November

      • Investor meetings in Nov/December

      • Legals, due diligence, etc


    • MAISY IS HERE! Team grew by 50%

    • Launched project xxx mid-October

    • [write any key event]…

  • Good

    • Remote team working well in autonomous fashion

    • Managed to open the round and secure funding during the quarter (blue star)

    • Learned a lot on the ambassadors / referral program

    • V1 still sells – can double down on it for now

    • Some of the big projects are live (ODT, V2)! Ready to iterate with smaller efforts

    • ODT launched

    • Website development is extremely fast and streamlined thanks to Webflow!!

    • V2 development much easier than V1

    • Collaboration between product and design started again

    • We have a lot of great long term ideas for growth and product

    • We have a simple way to pay rev share to anyone that wants to refer Tability (now we just have to find them!!)

    • Customer Stories! (blue star)

    • We have 3-4 more customer keen to do customer case studies

    • Work feels validated and we’re getting better at this!

  • 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)

    • Rushed on some of the big projects

    • Product design at a stand still

    • Long lead time for ambassador program, took up a lot of time

    • Not enough dev work or collaboration on V2

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

      • (but how do we keep it personal too?)

    • Not enough sales, counting too much on indirect leads

    • Funding took up SO MUCH TIME (blue star)

    • Not enough public pieces of feedback

    • Low activity to stay in touch with our community and customers

    • Not enough posts on socials / promotion of our created content

Going forward

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
    Contacting users rating us with a high NPS and requesting public reviews

  • Selling V1

  • 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

    Hiding V2
  • Weekly ritual (goals review → demos)

  • Writing down interviews and chat with customers/partners

  • More Product Design

    • Increase collaboration between dev and design

  • Thinking about our success in paid 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.