RPP Theme
Ensures RPP requests are provided by the Circle by a specific deadline.
FALSE
RPP Theme Based Discussion is different from the gTech RPP submission process.
RPP Theme Based Discussion is a Product Circle initiative to capture quarterly FR trends with Circle discussion and capture any AIs that we can contribute as a Product Circle like training (without PM/Eng intervention)
LS&R and BETA reviews are going to be merged as a single framework since they are mostly the same process and occur at the same time.
FALSE
Both processes do overlap in regards to the review workflow which is why they will be merged into a single Framework. However, the timelines for both are different (LS&R ~1 month / BETA ~6 weeks)
If a HC review is triggered/requested by a Tech-Writer, the Circle can do the review alone without the Tech-writer attending the session.
FALSE
If the Tech-Writer is requesting a HC review, they also need to participate in the meeting/session to review and address any content changes that may be requested.
However, keep in mind the Circle can still proactively review and request changes to a HC if there is a clear case for it without having to wait for the TW to initiate a review request.
The Consultant is solely responsible for motivating the circle into accomplishing the goals in time.
FALSE
Although the Facilitator can motivate the Circle to accomplish their goals on time. The lead is responsible for ensuring completion of all content related tasks.
Find common trends from the latest cycle of RPP requests.
TRUE
RPP Theme discussion allow Circles to share RPP trends, synthesize into themes, and come up with creative solutions w/o Engr intervention.
The Circle Lead should pull up launches list from go/launchtracker
TRUE
In the Lead/Consultant 2.0 context, the Lead will be responsible for pulling the list of launches from go/launchtracker prior to the LS&R review session.
However, if this is the first time the 'Lead' will be running this process, it is recommended the Consultant attends the meeting to help/advise with the process.
The core value of TW Reviews is to brainstorm any potential content improvements through challenging a Help Center article(s) in order to increase effectiveness
TRUE
Tech Writer reviews aim to solidify the collaboration between Product Circles and the tech writing team to find opportunities to improve external content for our publishers.
The Lead ensures group accomplishments are tracked and quantifiable (when feasible).
TRUE
Although the Consultant will help with the Success Tracker, it is the Lead's responsibility to ensure group accomplishments are tracked and quantifiable (when feasible).
Reviews RPP Requests provided by gPS, gCC to help PTM push for prioritization with Eng.
FALSE
Though PTM may use the RPP Theme discussion to bring feedback to Eng, the core goal is for the group to find non-Eng required solutions to address the RPP Theme needs.
PTM is responsible for validating each launch from the current review cycle that is added to the LS&R session agenda.
TRUE
PTMs are responsible for vetting the list of Launches for that Cycle prior to the Circle's session.
Tech-Writers are responsible for bringing and presenting HC articles at their corresponding Product Circle meeting for review.
TRUE
They will also solicit feedback in the meeting, ask for deeper reviews offline, and follow up with interested reviewers post-meeting.
The Lead is responsible for leveraging Product Expertise to guide content and efforts.
TRUE
The Consultant is not required to be a product expert in the Circle's vertical. The Lead on the other hand, should be the a knowledgeable Product expert able to guide content across the Circle's stakeholders.
It is required that Cycles provide at least 3 themes per RPP Cycle.
FALSE
We advise on at least 2-3 but there is no limit in regards to how many themes the group can come up with.
LS&R Review framework is ONLY responsible for:
- Flags training materials and gaps to PTMs.
- Coordinates joint trainings across gPS / gCC.
- Understands timelines implementations / handoffs / support.
- Implements comms plan for each local community. Who / when / where / how it will be performed.
FALSE
Though LS&R reviews include training and the communications tasks listed, they are not the only things the Cycle is responsible as there may also be further 'Infrastructure' and 'Knowledge / documentation' AIs.
Tech-Writers reviews within Product Circles reach a wider variety of reviewers than PC review.
One of the reasons why having Tech-Writer reviews in Product Circles is because of its diverse set of participants (e.g. PTM, TPE, TSMs, PCs).
TRUE
The reason why having Tech-Writer reviews in Product Circles is so beneficial is because of its diverse set of participants (e.g. PTM, TPE, TSMs, PCs) which they would not get in a PC or PTM only meeting.
The Lead is responsible for tracking the Circle's attendance and keep the member's list up to date so the Facilitator can update the web-site and mailing lists.
TRUE
Previously, it was the Facilitator's responsibility to track attendance, and keep the members list (as well as mailing lists, calendars) up to date. With the current changes (Lead/Consultant 2.0), the Lead should keep track of attendance and let the Consultant know if changes are needed.
RPP Theme workflow consists of:
Create the Jamboard
Consolidate asks
Discuss
Vote
Conclude w/ concise “tweets” for the Top themes.
TRUE
- Create the Jamboard: Facilitator kicks off the meeting by asking each business unit to note their 3 -5 asks on Jamboard
- Consolidate: Everyone starts grouping similar post-its together to emerge the overall trend
- Discuss: Everyone shares details on consolidated trend(s)
- Vote: Everyone votes upon the consolidated trends to surface the Top 2-3
Conclude: Generate the concise “tweet” for the Top 3 themes, and complete the output template
Besides Training and Communications, the following are expected during the LS&R Review process:
- Suggests additional Neo taxonomy entries to PTM to ensure optimal tracking of cases.
- Discusses if any troubleshooting tools creation or updates are required.
- Confirms if a new YAQS tag is needed.
- Reviews end to end workflow
- Suggests external HC updates to the Tech Writers
- Implements go/iheart updates
- Suggests vendor HC updates
TRUE
These tasks are all requirements (if applicable) for the LS&R Review process. They are part of the Infrastructure and Knowledge/Documentation updates that are part of the process.
The Consultant is responsible for identifying articles that need revision and reach out to Tech Writer in order to schedule the review session w/ the Circle.
Additionally, Consultants will be responsible for following up with the group once Tech-Writer makes changes to the discussed articles.
FALSE
Consultants are only responsible for their own Circles' success.
FALSE
Consultants are responsible for their own Circles as well as being an active member of the Product Circles working group, bringing ideas, providing feedback, and owning/creating Frameworks.
Additionally, Consultants are now responsible for advising other PAs that are implementing their own Product Circles.