Product Workflow
This document describes ttoss product workflow, focused on strategy, discovery, and definition of features that should be built. For the technical implementation process, see the engineering workflow.
Overview
Our product workflow is based on product development principles and has the main objective of defining what to build and why to build it, ensuring we deliver real value to users.
Workflow Structure
1. Goals
Objectives and principles that guide our product development process.
2. Kanban
Visual system to manage workflow and task status.
3. Meetings
Meeting structure for team alignment and communication.
4. FAQ
Frequently asked questions about the product workflow.
Product Workflow Focus
Strategy and Discovery
- User research: Understand real needs and problems
- Market analysis: Identify opportunities and trends
- Goal definition: Establish clear and measurable objectives
Definition and Prioritization
- User stories: Document requirements from user perspective
- Acceptance criteria: Define when a feature is ready
- Backlog management: Organize and prioritize what will be developed
Cross-Functional Collaboration
- Vision alignment: Ensure everyone understands the direction
- Effective communication: Facilitate information exchange between teams
- Decision making: Clear processes for product decisions
Workflow Differences
| Aspect | Product Workflow | Engineering Workflow |
|---|---|---|
| Main Focus | What and why to build | How and when to build |
| Responsibilities | Strategy, requirements, prioritization | Implementation, deployment, monitoring |
| Main Tools | ClickUp, research, analysis | GitHub, CI/CD, technical monitoring |
| Deliverables | User stories, backlogs, roadmaps | Code, deployments, features |
| Success Metrics | Product KPIs, user satisfaction | Code quality, cycle time |
Integration Points
The workflows connect at key moments:
- Task handoff: Product defines, engineering implements
- Technical feedback: Engineering informs about feasibility and effort
- Delivery validation: Product validates if criteria were met
- Joint monitoring: Tracking product and technical metrics
Next Steps
For product team members:
- Start with Goals to understand the principles
- Get familiar with our Kanban system
- Participate in structured meetings
Related Links
- Engineering Workflow - Technical implementation process
- Product Development Principles - Fundamental principles
- Product Strategy - Product strategy
- User Stories Guidelines - How to write user stories