Service Design - Ecosystem mapping

[rommel-agbay]

Ecosystem mapping will identify all the tasks/services supported by BC Registries including the program/stakeholder, channel, payment type, authentication type/account type, etc.

This will provide an overall view of the environment and help identify possible priorities for improving the service experience. Journey/Experience maps would be another valuable stream of work that will identify the different service experiences for users.

[rommel-agbay]

additionally focus on

• BCeID journey
• BC Services Card journey
• notary
• token with IDIM

[rommel-agbay]

possible outputs...

1. recommendations for possible updates based on initial scanning

   • places where the path ends and it's unsure how to complete - initiates a call
   • consistency in wording (i.e. title search company vs. service provider)
   • bigger questions - longer process/restorations - sometimes the checklist is on the webpage, sometimes it's just on the PDF - do we care? is this an opportunity to streamline? are there even enough visitors/users to these pages to make it worthwhile to update?

2. high-level map

3. with maps for each area? by registry? (Journey maps or Blueprints) - I need to spend some time with the data, meet with my colleagues.

   • weekly updates on progress and we can go from there

[rommel-agbay]

one-pager marketing deck - as a digital solution - value proposition for API service

• market scan
• how big of a market is it,
• partner value - journeys for people
• do they have api/screen scrape users - do they have legislative fees, authentication, etc. How can SBC support?

[rommel-agbay]

one-pager marketing deck - as a digital solution - value proposition for API service

• market scan
• how big of a market is it,
• partner value - journeys for people
• do they have api/screen scrape users - do they have legislative fees, authentication, etc. How can SBC support?

[rommel-agbay]

How does OrgBook BC fit into the ecosystem mapping/journeys?