Leveraging Adjacent Roles/Skills 19% Flashcards
A program roadmap
is a high level, strategic artifact, therefore, it should communicate where investments are being made and how you are directing your team’s efforts to achieve a goal that is aligned to the overall corporate objectives. Communication of your program roadmap is an opportunity to gain sponsorship, collaboration, and alignment from cross-disciplinary teams.
Types of product Roadmap
- An internal product roadmap communicates the effort and activities required to get your product ready for the market. This internal artifact is especially useful to coordinate across your engineering, marketing, sales, and support teams.
- A public product roadmap communicates the timeline when you will deliver the features to your customers. Architects and other stakeholders will use this information to plan their implementations and buying decisions.
Steps to create a roadmap
- Collaborate closely with each of the dependent teams identified in your roadmap.
- Start with a phased approach then address foundational items early – especially if these foundational actions are required to enable future, more transformational phases.
- Refer to your capability gap analysis for a list of all required changes. Place these items in your roadmap in a logical sequence identifying dependencies and any other critical path elements.
- Identify a roadmap hypothesis – Low hanging fruit first, BHAG first, self-funding etc. Then, maintaining the sequence/order, place each item from 3 in one of the phases by aligning with the business value impact.
- Remember to think big, start small, move fast!
- Behavioral economics
is a discipline examining how emotional, social and other factors affect human decision-making, which is not always rational. As users do not always have stable preferences or act in their best interests, designers can guide their decisions via strategic choice architecture—e.g., pricing structure.
● Framing/Anchoring
e.g.: the first number users see serves as a marker for judging other items’ values
● Defaulting
limit choices to 4 or less and prefill the option you’d like them to choose
○ Users will prefer a higher-priced baseline (to remove options from) over a lower-priced one (to add options to)
● Reciprocation/Power of Free
● Streamlining:
removing obstacles from processes (or adding obstacles to discourage unwanted behavior)
● Social Proof:
feeling like they are buying a popular item, or one used by an expert/celebrity usually bolsters their sense of security
● Attribute priming
ask users what features they want to help point them towards desired items
● Scarcity:
● Salience:
● Guard-railing:
● Tackling Loss Aversion:
- fear of loss raises the value of limited items in users’ minds
- appeal to customers with relevant add-ons before checkout
- keep users on track and make course-correction easy
- showcase potential gains and downplay outcomes (90% success rate > 10% failure rate)
Understand Process Mapping
- Process mapping creates visual representations of business processes. It includes any activity that defines what a business does, who is responsible for what, how standard business processes are completed, and how success is measured.
Benefits of Process Mapping
- Make understanding and communicating the process much easier among teams, stakeholders, or customers.
- Help identify flaws in the process and where improvements should be made.
- UPN
stands for Universal Process Notation and it is the simplest way of mapping business processes visually. By creating simple flows and diagrams, everyone in the company can understand how different aspects of the business works
Principles of UPN
- No more than 8-10 activity boxes on a screen
- Drill down from an activity box to a lower level to describe the detail
- Attach supporting information to an activity box
- View and edit controlled by access rights
- Version control and history of changes at a diagram level