Description
In Product, much of the job is taking the designs/ideas/opportunities/plans and interacting with stakeholders about those concepts.
Managing stakeholder's expectations, driving clarity to what is and isn't happening, as well as ensuring that folks are heard but making it clear when they have a voice and when they have a vote is vital.
This is the skill and subsequent behaviors where we will attempt to identify how we as a group and as individuals will continue to improve in this.
This ability is applicable to both Discovery (Design and Product Mangement) and Delivery (Product Ownership, Engineering, and QA).
Milestone 1
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability with only a small amount of guidance
- You actively seek clarity in the feedback that is given
 - You're able to follow most of our design/discovery/prioritization/planning review process effectively.
 
Milestone 2
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can employ this ability, with no assistance as well as being a trusted active or passive mentor to others
- Push back when appropriate, when feedback is out of alignment with user values or project goals
 - Leading a squad in identifying, coordinating, and scheduling times when feedback is being given by stakeholders
 - Setting the agenda or clarifying what feedback a squad is looking for in a feedback session (or in ad-hoc feedback sessions with stakeholders)
 - Having an understanding and following our full design/discovery/prioritization/planning process effectively
 
Milestone 3
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to multiple squads when wielding this ability, and therefore I would put them in situations where they can employ this ability as well as being considered an expert within this discipline
- Educating all of P&E on our design/discovery/prioritization/planning process and which stakeholders are ideally present at each stage
- Helping your squad and other squads identify which stakeholders to bring in and when (ad-hoc)
 
 - You actively seek feedback on your design/discovery/prioritization/planning product early and often
 - You identify gaps and help identify improvements to our standard ways of doing stakeholder and feedback management.
 
Milestone 4
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to a squad when wielding this ability, and therefore I would put them in situations where they can not only employ this ability but where they set the tone for this at the company level
- You create systems for effective feedback and stakeholder management
 - Your systems seek to include feedback from all avenues but prevents distraction to result
 - You design new and creative ways for external partners to influence our product
 - You influence executive-level members in the organization on how to effectively seek and manage feedback
 
Milestone 5
I have observed this person showing a consistent, comfortable, continuous, and clear positive impact to not just internal teams but the community/industry in general when wielding this ability, and they are recognized by the community/industry as an expert
- You influence executive-level members in the organization to continually educate on the value of the product design/discovery/prioritization/planning disciplines.
 - Speaks at conferences/meet-ups about how best to handle stakeholder feedback and management
 - Publishes articles/posts about best practices of stakeholder and feedback management
 
Configuration Health
- ✅ Associated with 10 roles
 - ✅ Has been referenced in 4 pieces of public recognition
 - ℹ️ No one has achieved a milestone on this ability
 
- ⛔️ Last updated: almost 6 years ago
 - ℹ️ Never conversed about
 
Role & Position Requirements
- Business Intelligence Analystsare recommended to be milestone 1+
 - Design Facilitatorsmust be milestone 2+
 - Design Reviewersmust be milestone 2+
 - Discovery Managersmust be milestone 2+
 - Feature Documentersare recommended to be milestone 1+
 - Launch Coordinatorsmust be milestone 2+
 - Managersmust be milestone 2+
 - Solution Designer (Ux Design)smust be milestone 2+
 - Solutions Engineersmust be milestone 2+
 - Ui Designersmust be milestone 1+
 
Examples / Observations
Observation created almost 5 years agoFeaturing:Stephen G.Engineering CommunicationInitiativeStakeholder / Feedback ManagementDevOps Enablement LeadUnexpected, concise, clear, communicated with both summaries and details, and action-oriented. As it pertains to emails about technical topics, it doesn't get much better than this.
I now feel that much more confident that Stephen isn't just thinking about doing the tasks he is assigned... he is thinking about the overall picture and health of Lessonly as we navigate this journey we are on.
Love it!!
Email #1:
HI everybody,
As you may or may not be aware there was a massive hack on solarwinds which provides infrastructure software to many companies. ( https://www.solarwinds.com/securityadvisory ).
I want to present to this group the (preliminary) findings as I investigated our exposure because industry-wide implications and more customers are going to be asking about this. It is going to be beneficial to have some sort of statement to respond with.
If you would like me to work with somebody on what that statement should be please let me know. And if you have any guidance on verbage before we craft such a statement I would appreciate it.
Executive Summary
We use a small unaffected Solarwinds product in non production environments. A couple of our vendors had similar exposure. Our biggest risk is Twilio which actually used an affected product, but they believe they were not impacted by the breach.
Our Direct Exposure
We do not use their software directly in our data centers.
PaperTrail
We use a product called PaperTrail in non-production environments for logging. No sensitive information should be sent there. This product
Vendors
Vendors known to have some exposure to SolarWinds Products
Twilio (Sendgrid, Twilio, Segment)
The company Twilio owns 3 services that we use. Twilio did use the affected software "in a limited fashion." They have been working with SolarWinds and believe they were ultimately unaffected by the breach
Twilio is our biggest risk, but at this point I believe it to be mitigated.
Harness
Harness used an unaffected SolarWinds product (Pingdom). Ultimately I see no risk here, but they did share this for transparency.
CloudBees (Codeship)
CloudBees owns the codeship product that we use. They, like Harness, used some unaffected SolarWinds products
Librato (scoped to our CodeShip product)
PaperTrail (scoped to our CodeShip product)
PingDom (basic external monitoring used by Ops)
Observation created over 5 years agoTalk about attention to detail, operational awareness, and excellent communication!
This was simply fantastic!!
Conversations about Stakeholder / Feedback Management
This section is for Lessonly folks only. Sign your team up to find your Gruuv!