Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Devportal Information Architecture: A 4-step Method

13 views

Published on

What information is essential for a devportal? How should it be structured? I’ll introduce a 4-step Information Architecture method. It focuses on the users (not just “developers”), the business strategy and the technical requirements and creates a roadmap that takes a team to and beyond their MVP.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Devportal Information Architecture: A 4-step Method

  1. 1. DEVPORTAL INFORMATION ARCHITECTURE A 4-step method Kata Nagygyörgy UX Strategist Mónika Alföldi-Zörgő Information Architect @MonikaZorgo monika@pronovix.com
  2. 2. 2 “Grow and help grow”
  3. 3. 3 My colleagues, who make it possible for me to be here
  4. 4. DISTILL & SHARE DEVELOPER PORTAL BEST PRACTICES 4
  5. 5. 5 IN THIS PRESENTATION Background Discovered methods Identified how the methods fit into the process and timeline Tweaked and shaped the process based on client feedbacks The 4-steps Based on the iterations 4 steps were identified Each building on each other What comes after IA? How to use the result of the IA workshop .
  6. 6. “ Nobody comes to your website just to look at your homepage or navigate your information architecture. People come because they want to get something done. 6 “Nobody comes to your website just to look at your homepage or navigate your information architecture. People come because they want to get something done.” (Ida Aalen, 2015.)
  7. 7. ● To create a resilient system ● Provide a lens to guide thinking and planning ● Getting to what to why ● Provide a great customer experience ● Content first approach 7 Our goal was
  8. 8. The Information Architecture phase of a Devportal 1 Website architecture analysis interview Inventory session 2 The information architecture workshop 3 Define next steps 4 8
  9. 9. Steps 1 Website architecture analysis interview Verify project and business goals Collect information about the users / target audience Inventory session Review and inventorize all the existing materials 2 The information architecture workshop Persona validation Element collection Element sorting Group naming Sitemap creation Storyboards User journeys Sitemap for the MVP 3 Define next steps We identify the missing contents and set up expectations for the possible next phases like design, content and development. 4
  10. 10. Step 1 1 Website architecture analysis interview Verify project and business goals Collect information about the users / target audience Inventory session Review and inventorise all the existing materials 2 The information architecture workshop Persona validation Element collection Element sorting Group naming Sitemap creation Storyboards User journeys Sitemap for the MVP 3 Define next steps We identify the missing contents and set up expectations for the possible next phases like design, content and development. 4
  11. 11. 1 Dev portal site goals - Describe the problems we solve with the portal 2 Target audience - Discover the client knowledge (data, user research) - Use the user's perspective as a main point of view - Core tasks the users need to accomplish, thinking holistically about goals - Proto-Personas 3 Analyze competition 4 Inspiration sites - Features and solutions you prefer 11 Interview Who? Product owner of the developer portal, a lead architect, possibly an API developer, someone from marketing, UX or any other stakeholders you can/want to involve. Where? Online What? Semi-structured interview
  12. 12. Step 2 1 Website architecture analysis interview Verify project and business goals Collect information about the users / target audience Inventory session Review and inventorize all the existing materials 2 The information architecture workshop Persona validation Element collection Element sorting Group naming Sitemap creation Storyboards User journeys Sitemap for the MVP 3 Define next steps We identify the missing contents and set up expectations for the possible next phases like design, content and development. 4
  13. 13. 13 Knowledge sharing sessions more than reference docs interface for your API initiative self-service hub for your API plays a key role as a trust signal
  14. 14. Inventory session 14 Who? Product owner of the developer portal, a lead architect, possibly an API developer, someone from marketing, UX or any other stakeholders you can/want to involve. Where? Online What? Discussion and online presentation Existing content Inspirational sites Website architecture analysis discussion Suggested elements Devportal Elements list
  15. 15. Step 3 1 Website architecture analysis interview Verify project and business goals Collect information about the users / target audience Inventory session Review and inventorize all the existing materials 2 The information architecture workshop Persona validation Element collection Element sorting Group naming Sitemap creation Storyboards User journeys Sitemap for the MVP 3 Define next steps We identify the missing contents and set up expectations for the possible next phases like design, content and development. 4
  16. 16. IA Workshop 16 Who? Product owner of the developer portal, a lead architect, possibly an API developer, someone from marketing, UX or any other stakeholders you can/want to involve. Where? Onsite (Online) What? Pre-planned workshop agenda ▪ 2-day workshop ▪ The steps are built on each other ▪ Goal to set up an IA based on the user tasks - Sitemap for the final site (full vision) - MVP sitemap ▪ We always keep our users in mind
  17. 17. Proto-Persona validation DAY 1 Element collection Sorting the inventory of elements Group naming Sitemap
  18. 18. Storyboards DAY 2 Discover stories on the sitemap MVP Sitemap
  19. 19. Step 4 1 Website architecture analysis interview Verify project and business goals Collect information about the users / target audience Inventory session Review and inventorize all the existing materials 2 The information architecture workshop Persona validation Element collection Element sorting Group naming Sitemap creation Storyboards User journeys Sitemap for the MVP 3 Define next steps We identify the missing contents and set up expectations for the possible next phases like design, content and development. 4
  20. 20. Define next steps 20 MVP SITE ELEMENTS Home 01 API catalog 02 Document ation 02 Quickstart guide 03 Conceptua l docs 03 FAQ 02 API detail page 1 03 Login/ Register 02 My apps 02 My Profile 03 Who? Product owner of the developer portal, a lead architect, possibly an API developer, someone from marketing, UX or any other stakeholders you can/want to involve. Where? Onsite What? Pre-planned workshop agenda
  21. 21. Define next steps 21 MVP SITE ELEMENTS CONTENT Home 01 API catalog 02 Document ation 02 Quickstart guide 03 Conceptua l docs 03 FAQ 02 API detail page 1 03 Login/ Register 02 My apps 02 My Profile 03 Existing content New content needed Templates
  22. 22. Define next steps 22 MVP SITE ELEMENTS CONTENT Home 01 API catalog 02 Document ation 02 Quickstart guide 03 Conceptua l docs 03 FAQ 02 API detail page 1 03 Login/ Register 02 My apps 02 My Profile 03 Existing content New content needed Templates DESIGN TEMPLATES UNIQUE DESIGN
  23. 23. Define next steps 23 MVP SITE ELEMENTS CONTENT Home 01 API catalog 02 Document ation 02 Quickstart guide 03 Conceptua l docs 03 FAQ 02 API detail page 1 03 Login/ Register 02 My apps 02 My Profile 03 Existing content New content needed Templates DESIGN DEVELOPMENT BACKEND FRONTEND
  24. 24. 24 Deliverables Workshop report Updated Proto-personas Sitemap for the final site Sitemap for the MVP User journeys on the sitemap Element list for the MVP pages
  25. 25. Thanks! Mónika Alföldi-Zörgő Information Architect monika@pronovix.com
  26. 26. Developer portal mailing list bit.ly/devportals 26
  27. 27. Image, screenshot and other attributions Unsplash.com

×