One project label cannot serve two incompatible histories once reporting and matching depend on it.
Finance needs a reconciled historical record while product engineering needs the new urgent-repair classification in the release.
Who you’d be doing this for
“I picked ‘urgent’ because the leak was spreading, and I needed someone today.”
Anders Moen · Homeowner
She is trying to hire a local professional for an unexpected plumbing repair, one of the requests affected by the urgent-repair classification.
What is at stake
Urgent-repair revenue and demand now move in opposite directions under competing project labels. You must weigh a fast release against an auditable history that downstream models can trust.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- financial auditability vs. release timing
- one project definition vs. backward compatibility
- historical consistency vs. BigQuery capacity
- model parity vs. rapid restatement
Why Thumbtack
Homeowner project classifications connect the request flow to pro lead value, marketplace measurement, and matching decisions.
Written with these in mind
Not your kind of problem? 72 more at Thumbtack, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.