Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
ProductONSers
Search
Matt Jukes
May 24, 2016
Technology
0
930
ProductONSers
Notes for ONS product owners
Matt Jukes
May 24, 2016
Tweet
Share
More Decks by Matt Jukes
See All by Matt Jukes
Roadmaps and Missions for the Scottish Digital Academy
jukesie
0
1.2k
A ChatGTP Christmas Quiz
jukesie
0
390
Jukes - User Manual
jukesie
0
150
my adidas
jukesie
1
410
This is a team sport
jukesie
0
490
Working in the open works
jukesie
1
74
Digital is a team sport
jukesie
0
610
The importance of being open
jukesie
1
89
The Wrong Users?
jukesie
0
620
Other Decks in Technology
See All in Technology
GitHub Issue Templates + Coding Agentで簡単みんなでIaC/Easy IaC for Everyone with GitHub Issue Templates + Coding Agent
aeonpeople
1
220
生成AIを活用した音声文字起こしシステムの2つの構築パターンについて
miu_crescent
PRO
2
190
予期せぬコストの急増を障害のように扱う――「コスト版ポストモーテム」の導入とその後の改善
muziyoshiz
1
1.8k
名刺メーカーDevグループ 紹介資料
sansan33
PRO
0
1k
OWASP Top 10:2025 リリースと 少しの日本語化にまつわる裏話
okdt
PRO
3
720
GitLab Duo Agent Platform × AGENTS.md で実現するSpec-Driven Development / GitLab Duo Agent Platform × AGENTS.md
n11sh1
0
130
Introduction to Sansan, inc / Sansan Global Development Center, Inc.
sansan33
PRO
0
3k
SREのプラクティスを用いた3領域同時 マネジメントへの挑戦 〜SRE・情シス・セキュリティを統合した チーム運営術〜
coconala_engineer
2
640
AIと新時代を切り拓く。これからのSREとメルカリIBISの挑戦
0gm
0
900
CDK対応したAWS DevOps Agentを試そう_20260201
masakiokuda
1
260
会社紹介資料 / Sansan Company Profile
sansan33
PRO
15
400k
Tebiki Engineering Team Deck
tebiki
0
24k
Featured
See All Featured
Hiding What from Whom? A Critical Review of the History of Programming languages for Music
tomoyanonymous
2
420
Primal Persuasion: How to Engage the Brain for Learning That Lasts
tmiket
0
250
Making the Leap to Tech Lead
cromwellryan
135
9.7k
Sharpening the Axe: The Primacy of Toolmaking
bcantrill
46
2.7k
We Have a Design System, Now What?
morganepeng
54
8k
SEO for Brand Visibility & Recognition
aleyda
0
4.2k
The AI Revolution Will Not Be Monopolized: How open-source beats economies of scale, even for LLMs
inesmontani
PRO
3
3k
Google's AI Overviews - The New Search
badams
0
900
How to build a perfect <img>
jonoalderson
1
4.9k
Bioeconomy Workshop: Dr. Julius Ecuru, Opportunities for a Bioeconomy in West Africa
akademiya2063
PRO
1
54
DevOps and Value Stream Thinking: Enabling flow, efficiency and business value
helenjbeal
1
94
The Organizational Zoo: Understanding Human Behavior Agility Through Metaphoric Constructive Conversations (based on the works of Arthur Shelley, Ph.D)
kimpetersen
PRO
0
240
Transcript
Being a Product Owner at the ONS. Beyond the job
description.
None
1.User Experience (UX) 2.Business 3.Technology 4.Team
1.User Experience (UX)
1.User Experience (UX) Learn how to undertake user research and
how to integrate it in to your decision making and prioritisation.
1.User Experience (UX) You are the voice of the user
in the product team so you will need to steer the priorities for the user researchers.
1.User Experience (UX) Observe as much user research as possible.
Ensure your team does this as well. Two hours every six weeks is target.
1.User Experience (UX) Read: https://userresearch.blog.gov.uk/2015/03/18/so-youre-going-to- be-a-user-researcher-top-tips-to-get-you-going/ https://www.gov.uk/service-manual/the-team/user-researcher http://www.disambiguity.com/guerrilla-empathy/
https://www.nngroup.com/articles/usability-101-introduction- to-usability/
1.User Experience (UX) Learn how to sketch ideas and use
basic prototyping tools to help the team visualise concepts.
1.User Experience (UX) Read: https://library.gv.com/the-product-design-sprint-diverge-day-2- c7a5df8e7cd0#.wneifj8h5 http://www.almostexact.com/ux-comics/ http://chrismcgrath.com/blog/keynote-is-best-app-prototyping-
tool https://library.gv.com/the-product-design-sprint-prototype- day-4-ebab764ac69f#.swf2wrufy
1.User Experience (UX) Be aware of the ‘visual language’ of
the ONS. You aren’t a designer but you will make design decisions.
1.User Experience (UX) Read: http://onsdigital.github.io/ons-pattern-library-starter/ http://www.bbc.co.uk/gel/articles/what-is-gel https://boagworld.com/design/pattern-library/
2.Business
2. Business Bring an understanding of the business process to
the team and a first hand knowledge of the user journey.
2. Business Bring a first hand understanding of the business
process to the team and knowledge of the user journey.
2. Business Understand the organisational environment. Who are the decision
makers, the stakeholders & the related teams.
2. Business Be the voice/face of the team internally. Make
sure there is sufficient communications activity. Too much is better than not enough.
2. Business Read: https://fitzdigital.wordpress.com/2015/09/21/showing-telling- plus-listening-collaborating-to-deliver/ https://gdsengagement.blog.gov.uk/2016/05/18/blog-like- there-arent-any-rules/ http://russelldavies.typepad.com/planning/2015/11/doing-
presentations.html https://medium.com/@jukesie/words-and- slides-2b2a8584e0f4#.ff5ucgif8
3.Technology
3. Technology Learn enough about the technology used in your
product that you can understand the high-level choices & trade-offs at a high level.
3. Technology Learn about version control (Git), collaborative programming (GitHub)
and at a high level how and when code gets deployed to users in your product.
3. Technology Read: http://mcfunley.com/choose-boring-technology https://blog.ons.digital/2016/01/20/technicalities-of-the-eq- alpha-outcomes-part-3/ https://guides.github.com/activities/hello-world/ https://18f.gsa.gov/2015/03/03/how-to-use-github-and-the- terminal-a-guide/ http://continuousdelivery.com/
4.Team
4. Team The Delivery Manager will make sure things get
done but you must decide what gets done and when.
4. Team You are responsible for articulating the product vision
and making certain your team works towards that goal.
4. Team Work collaboratively but the backlog is your
responsibility. Always prioritise with the user and the vision in mind.
4. Team Work with the Service Manager (or equivalent) to
produce a product roadmap. This is part planning artefact, part communication. Own it.
4. Team Make sure retrospectives happen regularly. If possible
invite Product Owners from other teams to facilitate.
4. Team Read: http://www.jamiearnold.com/blog/2014/07/07/everyone-loves- a-roadmap http://www.jamiearnold.com/blog/2015/02/17/how-to-scale- agile-service-delivery http://digital.nhs.uk/how-the-nhs-uk-team-does-agile https://www.gov.uk/service-manual/agile-delivery/agile-tools- techniques
http://www.scrumguides.org/scrum-guide.html#artifacts- productbacklog
You
Thanks. @jukesie