Facilitating holistic product decisions with information architecture
-
Upload
johanna-kollmann -
Category
Technology
-
view
175 -
download
1
Transcript of Facilitating holistic product decisions with information architecture
![Page 1: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/1.jpg)
Facilitating holistic product decisions
with information architecture
Johanna Kollmann | @johannakoll | IA Summit 2017, Vancouver
![Page 2: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/2.jpg)
![Page 3: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/3.jpg)
CHALLENGES
![Page 4: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/4.jpg)
“Multi-context” product
Website
Command-line tool
Integrations & notifications
![Page 6: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/6.jpg)
Mental Model
System Model
Conceptual Model
![Page 7: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/7.jpg)
We ended up designing “from the code layer out” - rather than having product intent drive the system.
![Page 8: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/8.jpg)
HOLISTIC PRODUCT THINKING
![Page 9: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/9.jpg)
CODE HAS IA
![Page 10: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/10.jpg)
1) Concepts and language in the code beat the best diagrams.
Lessons learned
![Page 11: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/11.jpg)
From an IA’s point-of-view:
• How will user journeys change?
• What’s the new hierarchy?
• Does our taxonomy still work?
• What do we call features and product concepts?
• Which words will make sense to users, what have we learned from research?
Scenario: scaling the product
![Page 12: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/12.jpg)
From an engineer’s point-of-view:
• How does the data model need to change to support this?
• How do existing code structures need to change?
• What do we call things in the code?
• What new services and capabilities will be required?
Scenario: scaling the product
![Page 13: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/13.jpg)
1) Concepts and language in the code beat the best diagrams.
2) Collaborate with system architects and engineers to ensure that concepts in the code match the product intent.
Lessons learned
![Page 14: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/14.jpg)
• Re-architect the code to match the conceptual model
• Can you use the terms that are user-facing in the code?
• It is what’s in the code that will be used and remembered
Build from the product layer in - not from the code layer out
![Page 15: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/15.jpg)
1) Concepts and language in the code beat the best diagrams.
2) Collaborate with system architects and engineers to ensure that concepts in the code match the product intent.
3) Engage with, and inform, the IA of your system architecture.
Lessons learned
![Page 16: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/16.jpg)
1) Concepts and language in the code beat the best diagrams.
2) Collaborate with system architects and engineers to ensure that concepts in the code match the product intent.
3) Engage with, and inform, the IA of your system architecture.
Lessons learned
![Page 17: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/17.jpg)
THINKING IN USER JOURNEYS IS HARD
![Page 18: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/18.jpg)
Objectives + metrics
Epics
User stories
Tasks
Customer Needs Business goals
Feature
Discovery phase Feature plan
![Page 19: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/19.jpg)
1) Concepts and language in the code beat the best diagrams.
2) Collaborate with system architects and engineers to ensure that concepts in the code match the product intent.
3) Engage with, and inform, the IA of your system architecture.
4)Feature testing can create a shared understanding of high-priority features.
Lessons learned
![Page 20: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/20.jpg)
Example credit: https://github.com/guidance-guarantee-programme/pension_guidance/blob/master/features/customer_booking_request.feature
Feature testing
• Written before you start coding
• Expressed in human language
• Facilitates understanding the feature
across the user journey
• Great for clarifying questions, easy to
collaborate on
![Page 21: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/21.jpg)
1) Concepts and language in the code beat the best diagrams.
2) Collaborate with system architects and engineers to ensure that concepts in the code match the product intent.
3) Engage with, and inform, the IA of your system architecture.
4) Feature testing can create a shared understanding of high-priority features.
5) Feature inventories that include engineering capabilities can provide a holistic overview across product and system architecture.
Lessons learned
![Page 22: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/22.jpg)
Feature inventory
• High-value core features
• Map against channels, integrations,
whatever your context requires
• Map system architecture (services,
capabilities) against features
• Will inform API development
![Page 23: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/23.jpg)
TAKE-AWAYS
![Page 24: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/24.jpg)
Semantics matter! The code has IA and drives your engineering colleagues’ conceptual model.
![Page 25: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/25.jpg)
Identify process points and tools that can connect the product and system architecture.
![Page 26: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/26.jpg)
1) Concepts and language in the code beat the best diagrams.
2) Collaborate with system architects and engineers to ensure that concepts in the code match the product intent.
3) Engage with, and inform, the IA of your system architecture.
4) Feature testing can create a shared understanding of high-priority features.
5) Feature inventories that include engineering capabilities can provide a holistic overview across product and system architecture.
Lessons learned
![Page 27: Facilitating holistic product decisions with information architecture](https://reader031.fdocuments.in/reader031/viewer/2022030306/58e4a6e71a28abbb038b494f/html5/thumbnails/27.jpg)
say hi: @johannakoll
THANKS MERCI DANKE