Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Revised PRODUCT DEVELOPMENT PROCESS

No description
by

Sebastian Cachia

on 28 November 2016

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Revised PRODUCT DEVELOPMENT PROCESS

PLANNING
& KICK-OFF

Briefing the team, clarifying the strategy, goals of the work for the coming cycle.
CODING
GO or NO-GO
RELEASE
PRODUCT DEVELOPMENT
PROCESS

EVALUATE
Did the project meet the hypothesis defined in the business case?
PM, PMM,
UX & RESEARCH
Post-release
- Evaluate project data
- Understand impact to Prezi
- Look at qualitative user impact

STRATEGIC
PLANNING

Get clearer on vision, define and develop mid-long term roadmap

STRATEGIC
DISCOVERY

Specify key questions, hypotheses for strategy,
Join user research, Validate hypotheses,
Impact estimates
PM
UX &
RESEARCH
What are the problems, needs and opportunities for target user/persona? Gain a better understanding of users and the overall context.
Gather and synthetize data to inform product strategy and planning
for 100%
A/B testing
Exploring new ideas
Optimize performances of features
PM responsible for this decision
UI, UX and the team
during development
DESIGN
Explore solutions how to enable user stories and define how features work and look like.
How do we do it?
How does it work?
How does it look like?
How does it integrate within the overall experience?

REVIEW
Get the whole team onboard, get everyone ideas, input and feedback to move forward
FEATURE
DEVELOPMENT

VALIDATION
Gain insights and learnings on actual performance of a proposed solution/idea
If there are other designers working on the project, the product team's uxr should be invited to that meeting and present the ux findings first.
brainstorming together
discussing ideas
design input
not design by committee
lead by the ui designer
PM
responsible
weeks
duration
6m
frequency
Bug reports, NPS, support reports
Research (surveys, field trips, phone interviews)
Early
research synthesis
, summary of insights and key findings to impact planning
Define strategic goals and value proposition
Project prioritisation
Transform discovery research into
product

backlog
Define
mid-long term

roadmap for each team

PM
UX &
RESEARCH
PM
responsible
2w
duration
6m
frequency
Discovery
research synthesis
, summary of insights and key findings
Persona descriptions
Persona scenarios
result
- Insights to bring into planning
- Draft personas and scenarios
- Draft Business Case
result
- Personas and Scenarios
- Long-term Roadmap
- Business Case
- High Level Product Backlog

Backed up by key
findings and insights
Refine user
stories and value proposition
Define cycle
roadmap
Define measurable
goals for the end of cycle
PM
UX &
RESEARCH
PM
responsible
1w
duration
2m
frequency
Specific, cycle-focused summary of insights and key findings
Define technical and performance requirements
Technical guidance to user stories and roadmap
Define measurable
goals for the end of cycle
TECHLEAD
This is a description of best practices, but at Prezi we don't have process for process sake, so we should use this ONLY WHEN it helps people to achieve better results

when a team fucks up because they knowingly decided to do faster and better way (and they did not succeed), they should help to explain why they did not succeed AND/OR how we could improve the process

this is a living document and will be improved
result
Roadmap
Brasks
UI
responsible
day(s)
duration
daily
frequency
result
ideas, concepts
high level sketches, wireframes
visual design mock-ups
prototypes
solution hypothesis
DESIGN
UX
!
result
UX reports weekly summary
1on1 talks/feedback with the designer/pm
UX
responsible
day(s)
duration
daily
frequency
Lab usability test (ppl coming in the office)
Remote testing
On site testing
Confirm hypothesis
UX
PM
responsible
1h
duration
daily
frequency
Decision about how we move forward
PM
UX
TECHLEAD
DESIGN
WHOLE TEAM
team discussion, anyone's ideas, opinions
feasibility, technical estimations
strategic feedback
result
Updated Brask paper
Ready for development
PM
responsible
1h
duration
ON DEMAND
frequency
PMM

WHOLE TEAM
team discussion
are we proud of the result?
do we have release blocker candidates?
discuss product-market readiness
review product marketing assets
Input
Company strategy
PMM
Market Sizing, Opportunity Assessment, Competitor Analysis
PMM
Collaborate on
Value Proposition
and project opportunity based prioritisation.
Initial
Marketing planning
, collaborate on
goal setting
DESIGN CRITIQUE
Receive focused feedback on the design
result
Focused feedback on current design stage
DESIGN
responsible
1h
duration
weekly
frequency
Walk participants through the design
Focus feedback on specific areas
Lead discussion
Collect feedback provided
DESIGN
PM
make decision
1 week
DISCOVERY
Dive in to the details for specific value propositions.
Who does this impact?
What are their problems, goals, jobs?
How would solving this problem change their life/workflows?
What are their key touchpoints?
-new user interviews
-review past research
-dig deeper into specific problems and value propositions.
UI
responsible
day(s)
duration
daily
frequency
result
pains, gains, jobs, goals
Refine user personas and scenarios
PM
UX
Design
Techlead
Sync to confirm product-market fit
Scope out content and asset work
PMM
BETA
RELEASE
STAKEHOLDER
COMMUNICATION
Keep all important stakeholders up to date
with team progress towards goals
result
Allignment on progress and next steps
PM
responsible
hours
duration
weekly
frequency
- Demo latest product changes to stakeholders
- Keep PMM up-to-date, check in about Marketing collateral
- Work with Data/Business-Model team on measurable goals
PM
Marketing
Go or NO-GO
PMM
responsible
ON DEMAND
frequency
Validate Hypothesis and QA product
Full transcript