This is a draft start to the worker proposals for the dashboard. It’s a living document for now:
In my view the worker proposal for the dashboard consists of the following examples:
Current
Strategic
Roadmap Feature Specs
Resource Planning
Development Feature Scope
Marketing Planning
Educational Planning
Metric Planning
Tactical Implementation
UX
Current Roadmap
QA
Bug Fixes
Development
Current Roadmap
QA
Bug Fixes
Marketing
Educational
Metrics
Future
Strategic
Product Refinement Plan (based on metrics)
Future Feature Roadmap Ideation and Creation
Resource Planning
Follow-on Marketing
Continual Metric Review
Tactical Implementation
Existing UX Tweaks
New UX
New Development
New Marketing Campaign
Educational based on new features
Ongoing
Steering Committee Working Sessions and Reporting
It requires the following resources regardless of where it lives structurally:
Product Owner
Product Management Resource
SME
UX Resource (to ensure tactical efforts do not bottleneck development)
Development Resource
Marketing Resource
Educational Resource
Steering Committee (from a directional input perspective)
Potentially: Business Relationship Arm
Questions:
What would be the differences in the two - Standalone vs. Underneath?
Is it ownership or reporting structure for example?
How will resources work across efforts?
What are the guardrails for decision making?
How does this work on multiple efforts? Like for example, I want to spend time on exploring new tech and opportunities
KPIs
The most important element
What do you consider success and failure of the worker proposal (details, a statement, a stake in the ground) - Quarterly - Define failure and raging success - Not sufficient to just be a bucket ..