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
● UPN
○ Resources are the “who” and are tagged with RACI
○ Additional levels of detail are indicated by shading on the upper-left corner
○ 2 main types of supporting information (attachments)
■ Implementation assets: requirements, user stories, Salesforce metadata, ERDs
■ Operational assets- notes, SOPs, help topics, metrics, links to apps
○ Number of levels of detail is determined by 3 drivers
■ Complexity
■ Regulatory requirements
■ User expertise
Other Process Diagrams
- Capability Model – Capability models or industry blueprints list out the high level process areas. These are useful for scoping out the specific area that you are mapping and to show the context within the overall business.
- Detailed Process Map – A detailed process map is a flowchart that shows a drill-down version of a process that contains all the details of each step of the process and any subsequent steps along the way.
- SIPOC – SIPOC stands for Suppliers, Inputs, Process, Outputs and Customers. SIPOC is a process mapping and improvement method that summarizes the inputs and outputs of one or more processes using a SIPOC diagram.
- Value Stream Map – A value stream map is used to visualize the flow of material and information that is needed to bring a product to the customer.
Tips to identify business process mapping tools and software
- Drag-and-drop interface
- Formatting capabilities
- Security and versioning
- Publishing and sharing capabilities
- Intuitive design
Business process mapping steps
- Identify the process you need to map
- Create a winning team
- Gather all necessary information
- Develop the process map
- Analyze the process map
- Develop new, better steps
- Manage the process
Best Practices of Process Mapping
- Apply business process mapping to the right types of processes
- Be clear about the focus of your process mapping
- Get someone skilled to map your processes
- Validate your maps.
- Don’t fix your processes until they are fully mapped
- Build the right team
- Keep it simple
- Work with your stakeholders
Why Business Analysis skills are important
- Business analysis increases Salesforce adoption
- Business analysis reduces rework
- Business analysis impacts architecture
- Business analysis increases agility and drives digital transformation
How you Build Trust
● Customers show their trust in 2 connected ways
○ Sharing their money
○ Sharing their data
● 3 keys to creating a data culture
○ Proficiency
■ Establishing training & education programs to build & scale data proficiency across the org
○ Agility
■ Creating access to trusted data sources, making it easier for anyone to find relevant data
○ Community
■ Creating a community and Center of Excellence to build internal data expertise
● 5 customer listening best practices
○ Create a voice-of-the-customer function & invest in listening at every level
○ Integrate insights into one narrative
○ Invest in intelligence and automation to aid accountability
○ Inspire a listening movement & psychological safety among employees
○ Close the loop
● Key actions to take
○ Establish a Data Culture and Center of Excellence
○ Create defined feedback loops
○ Build-in flexible, iterative cycles
Align on Your Impact Goals
● Steps
○ Everyone in the team writes what they hope the impact of the project will be on Post-it notes
○ Organize these on a vertical ‘ladder’
■ Long-term, significant, & hard to reach changes towards the top
■ Direct & easy to achieve changes towards the bottom
○ Use the Impact Ladder Worksheet to agree on and capture 2 statements
■ Impact- reflects the lasting social change of the project
● Draw from items from the top
■ Key Outcome- reflects a more near-term goal, an observable change or behavior that you want the people you’re designing for to achieve
○ Impact & Key Outcome statements serve as a north start for your design challenge
■ Help you to stay focused on your goals
■ Make sure key stakeholders are aligned with the team on these goals
AI Ethics Maturity Model
● Ethical AI Practice Maturity Model
○ Ad Hoc
○ Organized & Repeatable
○ Managed & Sustainable
○ Optimized & Innovative
● Salesforce Trusted AI Principles
○ Responsible
○ Accountable
○ Transparent
○ Empowering
○ Inclusive
● Responsible AI Development Lifecycle
○ Scope
○ Review
○ Test
○ Mitigate
○ Launch & Monitor
● FATE
○ Fair
○ Accountable
○ Transparent
○ Explainable
Drucker School - Organizational Change Leadership
● Manage with ambidexterity
○ Working on today’s needs as well as planning for the future
○ Drucker recommended that at least 10-20% of an executive’s time & resources be spent on the future
● Creative destruction
○ Successful organizations can eventually be replaced by more innovative ones
● 6 best practices of Change-Leading Organizations
1. Develop a Compelling Vision
a. Describes the purpose of the org & what it aspires to become to help customers succeed
2. Commit to Innovation
3. Focus on Customers & the Market
4. Dynamically Manage Organizational Capabilities & Resources
5. Practice Abandonment
a. Freeing up resources to lead change, rather than activities that no longer contribute to organizational success
b. If we were not in it already, would we be going into it now?
6. Create a Culture of Change
● In the Bridges model, change comes from the outside while transition happens inside
○ Change is situational- external forces create the need for change
○ Transition is psychological- how someone reacts to change
○ “External changes require people to make internal transitions”
● 8 steps to Successful Organizational Change
1. Establish a sense of urgency
2. Create a guiding coalition
3. Develop a clear shared vision
4. Communicate the vision
5. Empower people to act on the vision
6. Create short term wins
7. Consolidate & build on the gains
8. Institutionalize the change
● Top 5 things you can do to drive change
1. Understand how Salesforce enables organizational change
2. Develop a Systems Development Plan for your org
3. Adopt best practices for Systems Change Management
4. Drive user adoption
5. Be relentlessly positive, helpful, & determined
● TAM: Technology Acceptance Model
○ Perceived usefulness + perceived ease of use = higher likelihood of adoption
● WIIFM: what’s in it for me
