Stakeholder Mapping Quotes

We've searched our database for all the quotes and captions related to Stakeholder Mapping. Here they are! All 8 of them:

One of our recent studies revealed that while all reps start their sales efforts by mapping out stakeholders within the customer organization, core performers then move to what would seem like the logical next step—understanding needs and mapping solutions against those needs. But high performers do something very different. They extend this part of the sales process by digging into these individual stakeholders’ varying goals and biases, as well as business and personal objectives.
Matthew Dixon (The Challenger Sale: Taking Control of the Customer Conversation)
One potential anti-pattern is to make the business stakeholder take on the product ownership role.
Jeff Patton (User Story Mapping: Discover the Whole Story, Build the Right Product)
Thus social complexity is not just a function of the number of stakeholders – it is also a function of structural relationships among the stakeholders.
Jeff Conklin (Dialogue Mapping: Building Shared Understanding of Wicked Problems)
Phase 1: Discovery 1. Define the problem statement What is the challenge that will be solved? The problem statement is defined at this step and becomes the foundation of the project. Here is a sample problem statement: The company has more than one hundred thousand email addresses and has sent more than one million emails in the last twelve months, but open rates remain low at 8 percent, and sales attributed to email have remained flat since 2018. Based on current averages, a 2 percentage-point lift in email open rates could produce a $50,000 increase in sales over the next twelve months. It’s important to note that a strong and valid problem statement should include the value of solving the problem. This helps ensure that the project is worth the investment of resources and keeps everyone focused on the goal. 2. Build and prioritize the issues list What are the primary issues causing the problem? The issues are categorized into three to five primary groups and built into an issues tree. Sample issues could be: •​Low open rates •​Low click rates •​Low sales conversion rates 3. Identify and prioritize the key drivers. What factors are driving the issues and problem? Sample key drivers could include: •​List fatigue •​Email creatives •​Highly manual, human-driven processes •​Underutilized or missing marketing technology solutions •​Lack of list segmentation •​Lack of reporting and performance management •​Lack of personalization 4. Develop an initial hypothesis What is the preliminary road map to solving the problem? Here is a sample initial hypothesis: AI-powered technologies can be integrated to intelligently automate priority use cases that will drive email efficiency and performance. 5. Conduct discovery research What information can we gain about the problem, and potential solutions, from primary and secondary research? •​How are talent, technology, and strategy gaps impacting performance? •​What can be learned from interviews with stakeholders and secondary research related to the problem? Ask questions such as the following: •​What is the current understanding of AI within the organization? •​Does the executive team understand and support the goal of AI pilot projects?
Paul Roetzer (Marketing Artificial Intelligence: Ai, Marketing, and the Future of Business)
Sequencing and Pacing Is the work sequenced and synchronized properly? Are processes being performed too early or too late in the value stream? Are key stakeholders being engaged at the proper time? Can processes be performed concurrently (in parallel)? Would staggered starts improve flow? How can we balance the workload to achieve greater flow (via combining or dividing processes)? Do we need to consider segmenting the work by work type to achieve greater flow (with rotating but designated resources for defined periods of time)?
Karen Martin (Value Stream Mapping: How to Visualize Work and Align Leadership for Organizational Transformation)
In a section titled “Performance Factors,” Clint had been asked to indicate areas in which I’d exhibited significant strengths, as well as any areas needing development. There were only two areas in which he felt I needed development—organization (probably because he’d ridden in my car) and working more closely with third parties—but he had indicated six major strengths. The first three were creativity, achievement of objectives, and quality of work. No surprises there. The next three strengths—adaptability, communication, and autonomy—seemed a bit ironic. I scrolled down and saw my overall score: Very Good. By definition, this score meant that I had “exceeded objectives in several areas and required only occasional supervision.” I didn’t appreciate the real irony of Clint’s assessment until I looked at my stakeholder map and considered how I might have scored had Kristen conducted a similar evaluation at home. What score would I have received for adaptability? The review form defined this as “being open to change with new circumstances.” Going with the flow. We had just begun to work on my openness to change at home, and I was still learning how to adjust to this new mind-set. Meanwhile, at work, I presented myself as nothing if not adaptable. “Sure, I’ll take a new position on the marketing team.” “Of course I can stay until midnight tonight. Whatever it takes.” “Certainly, Clint, I’ll travel to customers every week. Anything else?” At home, Kristen asked me to help fold laundry and my head almost exploded. I guessed that I would receive Needs Development for that one. How about autonomy and initiative? Clint seemed to think that I was bursting with it, but Kristen would have offered a different opinion. “Initiative? Please. How is me having to remind you to turn off the television and play with the kids initiative? I’ll put you down for a Needs Development,” I imagined her saying. Achievement of objectives would have gotten me a high mark with Kristen, until I scrolled down farther and read the definition, which included the phrase “gets things done efficiently and in a timely manner.” I thought of the Christmas decorations drooping from our eaves. I thought of the countless times Kristen and I had been late for an engagement and she’d found me standing in my boxers in front of the mirror making faces.
David Finch (The Journal of Best Practices: A Memoir of Marriage, Asperger Syndrome, and One Man's Quest to Be a Better Husband)
Figure 1-9. Four principles. To serve memory and use, I’ve arranged these principles and practices into a mnemonic –STAR FINDER. In astronomy, a “star finder” or planisphere is a map of the night sky used for learning to identify stars and constellations. In this book, it’s a guide for finding goals, finding paths, and finding your way. First, we can get better at planning by making planning more social, tangible, agile, and reflective. At each step in the design of paths and goals, ask how these four principles might help. Social. Plan with people early and often. Engage family, friends, colleagues, customers, stakeholders, and mentors in the process. When we plan together, it’s easier to get started. Also, diversity grows empathy, sharing creates buy-in, and both expand options. Tangible. Get ideas out of your head. Sketches and prototypes let us see, hear, taste, smell, touch, share, and change what we think. When we render our mental models to distributed cognition and iterative design, we realise an intelligence greater than ourselves. Agile. Plan to improvise. Clarify the extent to which the goal, path, and process are fixed or flexible. Be aware of feedback and options. Know both the plan and change must happen. Embrace adventure. Reflective. Question paths, goals, and beliefs. Start and finish with a beginner’s mind. Try experiments to test hypotheses and metrics to spot errors. Use experience and metacognition to grow wisdom.
Peter Morville (Planning for Everything: The Design of Paths and Goals)
manipulation through the tactic of mass assignation. Silvia, a CIO for a logistics agency, described the tactic in the following manner. “Behind closed doors I assemble the team and we plan how to best maneuver the multitude of stakeholders we have to influence to get large-scale change done. We create a highly detailed power map that includes their priorities, relationships, likes, dislikes — even their hobbies and favorite foods. This power map file is encrypted and kept only on my personal laptop, which no one may access but me.” Then she explains, “We continuously analyze their communication styles and who they relate to both on and off the team to determine the best person, channel and information to sway them. If they need to meet with Paul on a project, but they dislike Paul but like Mary, for example, we have Mary set up the meeting and Paul just shows up with her. If they like golf, the information we provide them includes golf analogies. If they like seafood, I take them out for lunch at the local oyster bar. I learned to do this when I worked for a consumer products company. This is how we analyzed the relationships between multiple target customers at the same time to determine how to sell more, and it made sense to apply it internally here.” As noted, mass
Tina Nunno (The Wolf in CIO's Clothing: A Machiavellian Strategy for Successful IT Leadership)