[SCP 183] Product Workstream renewal Sept 2024 -February 2025

Mission:

Curate and propose a product roadmap based on research, user feedback/behavior, future market opportunities, collaboration with marquee communities, and an informed vision. Align with the mission and goals of the ShapeShift DAO and other workstreams for efficient execution.

TL;DR

I f you liked the team, goals, execution, and direction from March’s renewal then great this is the proposal for you!

High level changes are :

  • Hoff is moving to marketing, which is where he started. Congrats Hoff !
  • The budget is reducing topline slightly as a result.
  • We’re leaving contingency funds in the Product colony.
  • Tactical changes to goals particularly meeting with people 1:1, we missed bigly on that goal, motivating FBL.

Abstract -

As a product-centric DAO, the Product Workstream is accountable for a number of activities: cross workstream alignment on execution, retaining/acquiring users, growing the FOX ecosystem, speccing/launching new product lines, and achieving Shapeshift’s mission.

On product’s approval last year, governance approved the portfolio of bets and adaptive roadmapping. Though it wasn’t required we did a goals performance breakdown at the end of the year Product Goals Review Dec 1 and again this summer Goals 1 H 2024 Check in.

Just like last renewal, A YES vote verifies the budget and team continuing, and also support for product’s execution strategy namely:

  • Supporting for the strategy for 2024 “the themening” The themening A POB Sequel applying a portfolio of bets every quarter.
  • Approval of the 2nd half of the year’s goals Goals 1 half 2024 - #2 by 0xFBL and their metrics/KPIs. These goals continue with slight tactics tweaks and refreshed northstars.
  • An acknowledgement that all of this is flexible by design so we can capture market opportunities without putting granular items to vote or grand roadmap proposals.

Specification -

We track our goals at every office hours improving our documentation, rigor, and velocity. We produce artifacts every time, giving a snapshot of performance and a high level overview of what’s going on. Working with operations we publish a release thread almost every week Operations - ShapeShift

Onwards and upwards!

Revised Goals :

  • Goal 1: Iterate & Execute on the Portfolio of Bets (POB) utilizing Themes each quarter
  • Goal 2: Talk to Our Users & Deepen Ecosystem Partnerships
    • (FBL will grind for a stretch goal of 100 user interviews by march 1)
  • Goal 3: Refine Retention and Build Towards the North Star
    • (300 MM month-on-month volume north star)
  • Goal 4: Conduct Scoped Beneficial Experiments, Kill Under-performant ones, and remove app bloat.

Responsibilities

  • Prioritize and adjust the roadmap with cross workstream alignment.
  • Analyzing and surfacing new revenue streams that are not listed yet in the roadmap, but reporting back to the community with more details.
  • Coordinating research and resourcing in partnership with the FOX foundation.
  • Organizing and managing the roadmap, coordinating with engineering on timelines.
  • Removing blockers, assisting with product related decisions and keep things moving through the feature development process and Product/Engineering status updates throughout the week.
  • Product representation at the Weekly Ops Sprint.
  • Weekly release thread with operations.
  • Conducting user tests and mentoring other product team members to manage them on their own.
  • Facilitate bi-weekly office hours to provide updates on progress, report on KPIs for all initiatives, and offer space to the community to ask questions, give feedback, and pitch ideas.
  • Draft product specs, reviewing designs, work with ENG workstream to evaluate engineering resources, and iterate the feature development process.
  • Hosting and Leading Spec kickoffs/spikes/breakdowns between Product and Engineering.
  • Spinning up regular retros (at either phase completion or large feature completeness)
  • Leading and continuing all scheduled team syncs and 1-on-1s.
  • Managing Budget and workstream contributor payments made through Colony.
  • Coordinating strategy sessions, touchpoint, and retros for launches. Facilitating where necessary.

Budget and team

The Product workstream will consist of 3 members all full-time.

Screenshot 2024-08-19 at 5.23.07 PM

The total budget Breakdown of September- February

Monthly:

$34400 (6% less)

$6600 (USD in FOX — 16% decrease)

$41,000 TOTAL

Totals come out to:

$209,214

$39,600 USD of FOX (including $2400 in FOX for user testing)

$248,814. TOTAL

This is the previous total budget:

previous budget

The change to the DAO topline budget is 6% less.

Screenshot 2024-08-19 at 5.33.56 PM

The addendums are the earmarked SaaS budget and the retained events budget.:

  • SaaS
    • Figma [$69 a mo for the team]
  • current funds: [$2454] —> continue holding funds in colony.
    • previously we earmarked $200 a team member for flight or stipend to ETH denver and kept a small contingency. No one went to denver, so we’ll leave these contingency funds for now. Those should be helpful for any additional SaaS we may trial or any work product would like to contract that requires USDC

Benefits -

  • Unlocks new features, continues alignment with a strategic lens, and continues execution of the product team’s goals.
  • Unblocks engineering and ships the roadmap,
  • Gets the roadmap going in iterative loops, with extra hand holding by FBL
  • executes quarterly with full transparency for Governance.

Drawbacks -

  • We’re moving with more rigor so we aren’t shipping as many shiny features.
  • Our team is lean so there is only so many resources to cross allocate
3 Likes

Thanks for writing and submitting this renewal proposal! Definitely a good idea to listen to more of our users and potential users.

Would it be possible to include a full breakdown of the budget as you did last renewal please?

Cheers and thank ya.

Hmm i realize my math might not have mathed on a cell. Will edit that on the final proposal so they sum correctly. Here is the google sheet for reference

For forum transprency, i spent a hell of a time trying to use the engineering fox grants and move to that structure. Hopefully On the next renewal, we can use something similar so there is unified accounting and better TC for all teams across the DAO. As is, boosted FOX is slightly better month on month and on net for both contributors and the DAO writ large.

Not to shabby boosted FOX not to shabby.

2 Likes

Thanks for the link and details!

1 Like

Im not a fan of the Fox grant setup. Besides when it was setup everyone said noone else could do this, but we didnt stick to that for long. lol.

Anyhow, snapshot giving me issues this morning, so ill have to try again later.
Thanks for being a PITA fbl and pushing all the edges. Seems we get to discuss more sometimes cuz of it.

1 Like

PITA workstream would be an awesome idea.

I would vote for you to be the Head of the PITA department!
Like having one of those ‘grenades with the sign , pull here to ring complaint department’ signs? heh

1 Like