How to Create a Slide Deck from Your PostHog Insights with Nouswise AI
To create a slide deck from PostHog, connect the service in Nouswise, enable the relevant source, and use Computer to request the output. This guide focuses on product review presentation for product leadership and growth teams.
Why product reviews need a decision
A product review can consume its meeting time explaining dashboard filters. An effective PostHog slide deck gives the audience the metric definitions up front, shows comparable segments, and leaves time to choose the next experiment. Its job is to support a decision the team is ready to make.
McKinsey’s analytics research emphasizes choosing valuable business problems and connecting analytics work to adoption. For a product review, that means stating which experiment or resource decision the presentation is meant to support.
A practical example
A SaaS product team is reviewing activation and retention across customer segments. The meeting needs to choose one experiment for the next cycle. An eight-slide deck could show the strongest observed change, the tracking caveat, and the proposed success measure. This is an illustrative product-review scenario.
How Nouswise helps with this task
Ask Nouswise to build a focused presentation from the selected PostHog insights. Limit the deck to the decision at hand and request report references for each figure. The analyst checks comparability; the product team decides which hypothesis to test.
Prepare the source material
Select the relevant reports, time windows, segments, and metric definitions. Confirm that your connected account can access the selected records. Connector actions and available data depend on the service and your authorized account.
The images show the end-to-end product workflow. The labels in this guide follow the interface, including Research and Computer.
Step 1: Create the connection
In Nouswise, go to Settings → Connections → New Connection. Enter a recognizable name such as Product insights, choose PostHog, and select Create. The name helps you identify the right account when more than one connection exists.
Step 2: Authorize access
Use Authorize on the new connection and complete the service’s authorization flow. The connection can be shared for organization users through one authorization, or each user can authorize their own account. Choose the model that matches your team’s access rules and the data in this guide.
Step 3: Enable the named connection
Open Sources and enable Product insights, the connection created for PostHog. Confirm that its account has access to the material for this task. You can turn the source off when the assignment is finished.
Step 4: Give Nouswise a precise task
Use Research when you want an answer to a question. To create a slide deck, choose Computer and describe the finished deliverable. Specify the audience, slide count, comparison period, segments, and experiment decision. Ask for a chart source on every slide that uses a number.
Create an eight-slide product review deck from the selected PostHog activation and retention insights for the last month. Define each metric and segment, compare with the previous month, distinguish tracking changes from behavior changes, and propose one next experiment. Cite the report behind every chart and mark causal explanations as hypotheses.
Step 5: Follow the task’s progress
The task plan is Read PostHog reports → Verify event definitions → Compare segments → Outline insight story → Build slide deck → Verify figures. Open the progress graph to see which stage is running. Longer tasks may continue in the background while you work elsewhere; return to the task to inspect the result. The actual plan can vary with the available sources and the request.
Step 6: Review the slide deck
When the task is ready, open the slide deck, check each value and denominator against PostHog, and confirm that event-definition changes are called out. Have the product analyst approve the metrics before presenting. Download the reviewed PPTX or PNG version for the meeting.
What a useful result should contain
Part of the output | What to look for |
|---|---|
Definition slide | Metric, denominator, segment, and date window |
Finding slides | Comparable observations with chart source references |
Decision slide | Experiment, success metric, owner, and review point |
Track whether the review ends with an experiment owner and success criterion, and how many metric corrections are needed after the meeting.
Related guides
Frequently asked questions
How many charts belong in a product review deck?
Use only the charts needed to support the decision. Put detailed exploration in a companion brief rather than filling every slide with dashboard captures.
Can the deck claim a release caused a retention change?
Only with suitable supporting analysis. A timing association is a hypothesis, and tracking or cohort changes should be checked first.
What should the final slide ask the audience to do?
State the proposed experiment or decision, its owner, and the measure that will determine whether it worked.
Written by:
Nouswise Technical Team
Share with friends:
