Feature Fridays

Professional, approachable sessions that help people understand a feature, see it work and confidently use or demonstrate it.

Planning draft. Session dates, presenters and invitations are not scheduled. Current client-facing previews retain their Coming Soon status.

1. One content source, different ways to use it

Reuse the existing editable presentations, cleared screenshots, narration, short videos and customer guides. Build a modular presentation so a consultant can select a feature, a module or a release segment and place it within the main sales presentation. Keep a consistent opening, customer-value explanation and closing action.

The current materials are reusable; a complete comparison with the master QA/sales presentation is still outstanding. Do not describe that alignment as already verified.

Material	Purpose and audience	Reuse approach
Core feature deck and demo	Staff, invited partners and client users	One approved story with relevant examples and a clear release status.
Participant handout	Everyone attending	One or two pages: outcomes, three practical actions, useful questions and links to the full guide.
Internal trainer manual	Consultants, internal support, QA and presenters	A separate concise guide per module: workflow, roles, configuration, troubleshooting and known limits.
Implementation appendix	Authorised internal or partner implementers	Selected technical settings and deployment guidance appropriate to their role.
Consultant demo kit	Consultants preparing client meetings	Short and detailed slides, talk track, demo reset steps, expected results, common questions and a recorded fallback.

HRFocus Launch Content now includes the separate internal trainer guide and consultant demo handoff by default for full module packs. Explicit single-asset requests remain scoped.

2. A repeatable 30-minute session

Time	Segment	Expected result
0-2 minutes	Why this matters	One everyday problem and the practical benefit.
2-12 minutes	Show the workflow	One clear end-to-end journey using the current screen and fictional Star Wars data.
12-17 minutes	What makes it work	Key roles and choices. Use the technical appendix only when appropriate to the audience.
17-20 minutes	Try it or predict the next step	One small exercise or a guided question, suitable for the attendees.
20-30 minutes	Questions and next steps	Clarify what is available, log unanswered questions and point to the right guide.

Use a live system, a document-led walkthrough or the existing video according to the session. Keep the same learning outcome in every format. Use a co-host to collect questions during the demonstration.

3. Internal manual structure

Aim for four to eight useful pages per module, without padding. The manual should help a colleague teach, demonstrate and support the feature. Link to the detailed user and configuration manuals instead of copying them.

What the module does, who uses it and which business problem it addresses.
A one-page workflow map and the roles involved.
Three important tasks with current screenshots, expected results and a short talk track.
Important configuration: admin location, key setting, initial default versus runtime fallback, permissions and prerequisites.
Common questions, likely mistakes, troubleshooting and when to escalate.
A short practice exercise, verification checklist and known acceptance limits.

4. Proposed opening sequence

Order	Topic	Demonstration focus	Readiness
1	Support Intelligence	Capture a request, assigned-ticket handling, public/internal feedback, history, on-behalf capture, FAQ guidance and branded export.	Current guides, decks, videos and separate internal trainer guide ready.
2	Chatbot 2.0	Useful questions, sources and actions, supported visuals and filters, documents, feedback and the route from a Knowledge gap to reviewed content.	Current manuals, employee guide and separate internal trainer guide ready.
3	Report Portal 2.0	Published sources, company/employee joins, fields, filters, charts, saving and background results.	Confirm the complete walkthrough and current save/reopen acceptance before the session.
4	Manager Workspace	Team priorities, directory, leave, performance overview and staff requisitions.	Select a bounded story and verify current role access.
5	Employee Home and Talent Planning	Everyday KPIs, light/dark experience and a handoff to the dedicated talent story.	Use a short overview; detailed talent content remains a separate pack.
Later	Performance and Employee Relations	Dedicated module workflows.	Keep gated until the requested module adjustments and QA are complete.
End of release series	Release overview and configuration clinic	Connect the changes and explain new implementation choices.	Combined guide and CEO one-, two- and five-minute overviews remain at the end.

5. Reuse in client and partner presentations

Select the short overview for an introduction, then only the relevant detailed section and native demonstration.
Retain the current branding, transparent logos, consistent theme and source module identity when inserting slides into the master deck.
Keep Coming Soon labels until the relevant feature is released. Match the claims to the demonstrated version and client configuration.
Keep internal diagnostic notes separate from the participant handout. Share implementation details with the appropriate technical audience.
Use fictional names, positions and contact details. Recheck screenshots and the live account before a client session.
Provide a clear closing action: try the feature, review its configuration, or arrange a focused demonstration.

6. Make it relaxed and professional

Use clear language, a clean title slide, readable screenshots and one practical outcome. A light Star Wars example can make the session memorable without distracting from the business workflow. Introduce the presenter and module, keep to time, invite questions and close with useful follow-up links.

Start with a two-session pilot, then keep a regular Friday slot if the attendance and preparation effort justify it. Choose the invited audience for each topic; every session does not need to suit every role.

7. Feedback and follow-through

Capture one confidence question before and after, the most useful action learned, and unanswered questions. Keep feedback as observations rather than invented time-saving or adoption figures. Assign a module owner to follow up; turn recurring questions into reviewed Knowledge or FAQ content where appropriate.

Use the internal Hub for staff resources. Provide an appropriate approved participant pack or externally accessible location for invited clients and partners; a local-machine Hub URL is not an external distribution link.

8. Saved next actions

Compare the reusable module slides with the master QA/sales deck and agree shared opening, section dividers and closing slides.
Use the completed separate Support and Chatbot trainer guides alongside the full manuals.
Prepare one participant handout and a short presenter rehearsal for the Support pilot.
Choose the session owner, co-host, first date and audience, then arrange invitations.
Record the approved core session if useful and capture questions for the next revision.

Owners are Unassigned until agreed. No invitations, calendar entries, external publication or new rendered training videos have been created by this plan.