Product · Teams, Skills and Capacity

Who can do the work.
When it can be done.

Every hour your team has, pointed at the work that moves the number. Nothing is committed that nobody can do, and no date is written from wishful thinking. People record their skills and their time, Symphiq proposes who takes each recommendation and dates the rest from real capacity, and you accept every step. Capacity is time people enter, not time we measure.

One proposed recommendationREC-101 · Reduce mobile checkout frictionProposed · not yet owned
The work asks forCRO at Advanced · Analytics · Payment-method QA
Who holds those skillsMaya Chen · CRO 4/5; Analytics 4/5 · Says she has 60% of her time for this shopLiam Brooks · Product UX 3/5; Content 4/5 · Says he has 40% of his time for this shopNorthstar Growth · CRO 4/5; Paid Media 5/5 · Says they have 30% of their time for this shop
GapNobody holds Payment QA. The team confirmed it depends on an external provider.
OwnershipWaiting for a person to decide.

From skills to schedule

Five steps. Your people fill in the first two, and the plan gets more honest with each one after them.

  1. My skills Everyone records the skills they have, and how strong they are.
  2. Teams Group people into teams. Add an agency or freelancer as extra capacity and skills.
  3. Staff work Symphiq proposes which team takes which recommendation. You review and apply.
  4. An honest plan Work no team can do is left out by default. Still visible, and you can overrule it.
  5. Schedule my plan Real start and end dates from each team’s capacity. Teams work in parallel.

Behind the dates: a day-by-day ledger of each team's committed time. Teams can work on several things at once, never past the time they have.

No wasted commitments
Work only lands where someone can actually do it.
Hiring from evidence
The gap is named while it is still a decision, so you know what to hire for before it costs you months.
A plan that survives a resignation
When someone leaves, the plan re-packs around who remains, and you accept the new dates.
Agencies count as capacity
Outside help joins the same schedule without needing accounts.

A skill is a match, not a label

The work

Every recommendation lists the skills it requires, and how strong each one has to be.

  • Conversion optimisationAdvanced
  • Paid mediaAdvanced
Your people

Every person lists the skills they hold, at the same levels.

  • Maya ChenAdvanced
  • Northstar GrowthAdvanced

Teams inherit the skills of their members, plus anything the team declares.

That match, skill for skill and level for level, is what staffing means here. Skills decide whether the work can be done. Capacity decides when.

Name the gap while the work is still a decision, not to score people

CRO · Advanced Covered
Maya Chen holds it at Advanced. Northstar Growth also holds it.
Analytics · Advanced Partly covered
Maya Chen holds Analytics, but needs Advanced and holds Intermediate.
Payment-method QA Not staffed
No team holds it. The team confirmed it depends on an external provider.

Capacity is time, not talent

How much working time a team can give, entered by people rather than measured: who is on it, how much of their time it gets, plus any outside help you add.

Allocation

60% of Maya’s time goes to Growth

Set by a person, changeable by a person.
Outside help

Northstar Growth · 0.45 FTE

Agencies and freelancers count as capacity without needing accounts.
Availability

Liam is away in March

His time drops out of the plan; his skills do not. If someone leaves, the plan re-packs around who remains, and dates you set by hand stay put.

No timesheets. No measured availability. No utilization tracking.

Symphiq proposes the plan. You accept it.

Staff work proposes who. The schedule proposes when. Nothing is assigned and no date is written until a person accepts it.

Work no team can do is left out of the schedule by default: visible, overridable, and the override is recorded.

Symphiq proposes. You decide.

The recorded decision
Maya Chen owns REC-101. The team accepted the proposed dates, and chose to start after payment-method QA clears the external dependency they confirmed.
Decided by the team · not by Symphiq

See who on your team can take the first recommendation

Connect GA4 and Shopify, set your revenue target, and the roadmap builds against it. Add your team when you are ready.

Answers

It proposes. Staff work suggests which team fits each recommendation, and you apply or change it. Nothing is assigned until a person accepts it.

Capacity is based on estimates people enter or adjust. It is not measured availability, a timesheet, or workforce surveillance.

It stays visible, but it is left out of the schedule by default and the missing skill is named. You can start it anyway, and that decision is recorded.

Yes. Roles and permissions control participation, while people remain responsible for the assignments and commitments they make.

Unlimited seats let the people who need context participate in the same roadmap, while roles control what each person can change.

See Work and Outcomes