Skip to content
Gallery
Product Operating Rhythm
How to lead more effectively with a well designed Product Operating Rhythm
Charter & Resources
Launch Calendar
More
Share
Explore

icon picker
Charter & Resources

Problem’s we’re solving and the resources we're allocating to solve those problems.

💡 Some tips:

Focus on the problems your product team should be solving.
Update the vision as needed.
Don’t bring metrics too early into the team charter. Leave them for OKRs
No more than 5 OKRs per area.
⁠
Here is an example of how the Marketplace Dynamics team was built out and chartered at Thumbtack. Sub-teams were organized around each of these problems. Those building blocks were then used for quarterly goals and resourcing. Please note that all of this was recreated from memory several years after having originally worked on it; the key is to spend the time synthesizing and distilling to the right level of granularity.

Mission/Vision

The marketplace dynamics team is responsible for building out the systems that allow the right connections to happen across the two sides of the marketplace (pros and customers)

Guiding Principles

We are building out a platform. The systems we build need to scale across hundreds of categories.
We aim to build a system that requires less and less human input over time. The data we’re generating is a strategic asset and we aim to build systems that tune themselves the more they get used.
We aim to eliminate “trade-offs” as we build out our systems. We believe that we can build a marketplace dynamic that grows the overall pie for customers, pros and Thumbtack.
Main problems to solve
1
Matching Customers to the right set of responsive Pros
2
A Pricing system that aligns incentives across the marketplace
3
A trust and safety system that protects pros and customers from bad matches.
There are no rows in this table
⁠

Resources to solve problems

Note: To edit/add teams, go to the
Estimated team size required for project
⁠
table below this table
Problem
QX OKRs
Status
Notes
Team
Est. FTEs
Matching Customers to the right set of responsive Pros
Improve successful response rate by Y%
Not Started
​
Engineering
3.0
Design finalized for new taxonomy hierarchy
Not Started
​
Product
4.0
​
​
​
Marketing
5.0
​
​
​
Sales
2.0
​
​
​
Operations
1.0
A Pricing system that aligns incentives across the marketplace
Launch a feedback system for pricing irregularities
Not Started
​
Engineering
2.0
​
​
​
Product
6.0
​
​
​
Marketing
2.0
​
​
​
Sales
7.0
​
​
​
Operations
3.0
A trust and safety system that protects pros and customers from bad matches.
Reduce Spam by Z%
Not Started
​
Engineering
3.0
X% of incidents resolved within 3 days
Not Started
​
Product
7.0
​
​
​
Marketing
5.0
​
​
​
Sales
4.0
​
​
​
Operations
2.0
⁠

Estimated team size required for project
Team name
Total Estimate FTEs
1
Engineering
8.0
2
Product
17.0
3
Marketing
12.0
4
Sales
13.0
5
Operations
6.0
There are no rows in this table
⁠

⁠

👉 Next:
Launch Calendar
⁠
⁠

⁠

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.