Move this Jira to your team's Jira backlog for execution.
Schedule a meeting(s) with your stakeholders.
It might require more than one meeting to ensure you communicate to all stakeholders.
Invite Nick Fernholz (nfernhol@redhat.com) as optional to this meeting. Do not worry if Nick is not available, just please add him and he will try his best to attend. You do not need to contact Nick Fernholz for any reasons around this meeting.
Your meeting must include one of the following DocX CS. If you have not started any engagement with a DocX CS or been assigned a primary DocX CS to work with, invite the DocX CS that is assigned to monitor the #ccs-jtbd-doers slack channel for the week of your scheduled stake holder meeting.
Stephanie Sout (sstout@redhat.com)
Tanya Shearon (tshearon@redhat.com)
Heather Joy (hjoy@redhat.com)
Preeti Chandrashekar (pchandra@redhat.com)
Close this Jira after the meeting(s) has been scheduled. *NOTE: It is not required that these meetings occur in Q4, just that they are scheduled. Due to holiday/PTO it's possible you will need to schedule them for January.
Notes
Identify a strategic flow of comms to your stakeholders. This step may vary per team but we want to provide some things to consider.
Who should get buy-in first? Typically, whoever has the most high-level, strategic view is a good starting point. Their buy-in and engagement will trickle down to folks who are more execution-focused and may be more nervous about the change.
Is there anyone who you feel will be more challenging to get on board and may need some more focused Q&A time?
For example, maybe you have a PdM Manager assigned to your product who is very strategic who you can explain this to first. Then, you can pull in other Product and Eng leads.
If your stakeholder team is small, or you already have a great relationship, it's possible having one meeting with everyone is the right move.
Use your judgment, and talk to your manager if you need help navigating the stakeholders for your product.
Practice the presentation!
Do a dry run with others or record yourself
Prepare to refresh your memory if you are holding the meetings in Q1
Questions?
If you have any questions, use the private JTBD Doers Slack channel: #ccs-jtbd-doers and tag the DocX CS that is assigned for the time frame of your request in this spreadsheet.
The slack channel #ccs-jtbd-doers is only for associates that are working on JTBD JIRAs. If you do not have access, please contact the DocX CS that is assigned for the time frame of your request in this spreadsheet.
Task
Critical