Apps and Demand Planning

Apps and Demand Planning

DashboardGenius Apps are for workflows that need more structure than a normal chat thread.

Use an app when the work needs a stable review surface, clear steps, saved working state, or a formal handoff.

What Apps Are For

Apps keep the same connected data model behind DashboardGenius, but present it in a workflow-specific surface.

That is useful when a team needs to:

• review the same operating process repeatedly
• keep versioned working state inside DashboardGenius
• compare iterations without rebuilding the analysis
• prepare a handoff artifact for downstream execution

Apps do not replace chat. They are best when the workflow itself matters, not just the answer.

Chat vs Widgets vs Apps

Use chat when:

• the question is exploratory
• the user needs a quick answer
• the path is not known yet

Use widgets when:

• the workflow repeats often
• the team wants stronger starting structure
• the result should still flow naturally into a normal thread

Use Apps when:

• the team needs a multi-step review process
• people must return to the same working state later
• version comparison or handoff readiness matters

Current App Surface

DashboardGenius currently includes an Apps area with Demand Planning as the live workflow.

Demand Planning is designed for planning teams that need to review inputs, adjust an in-product working version, assess risk, and prepare a cleaner handoff before the work leaves DashboardGenius.

When to Use Demand Planning

Demand Planning is a strong fit when your team needs to:

• review a weekly or near-term demand plan
• compare forecast, targets, actuals, inventory, and schedule context
• make DG-side planning adjustments before exporting a handoff
• document risks and planner caveats in one place

It is especially useful when the planning conversation currently lives across multiple sheets, dashboards, and side notes.

Typical Inputs

Demand Planning can pull together roles such as:

• forecast or demand signal inputs
• targets
• production schedule context
• sales actuals
• inventory context
• planner notes and caveats

The exact connected sources vary by organization, but the goal is the same: review the planning picture in one structured workflow instead of stitching it together manually each time.

The Demand Planning Workflow

The current flow is organized into six practical review areas:

1. Workflow

Use this view to understand the overall state of the current working version:

• source health
• planner adjustments
• risk counts
• export readiness

This is the fastest place to see whether the version still needs review before handoff.

2. Sources

Use Sources to review which connected inputs shaped the current working version.

Check:

• whether the expected sources are present
• which business role each source is filling
• whether freshness and trust look reasonable
• whether anything is missing before you review demand

This step is useful because bad source assumptions create planning errors that no amount of downstream polishing will fix.

3. Planned Demand

Use Planned Demand to inspect demand rows and make DG-side adjustments.

Typical review work includes:

• checking baseline demand
• reviewing target and promo adjustments
• adding planner adjustments
• documenting planner notes
• confirming the version is ready to move to risk review

These edits stay inside DashboardGenius until you export a handoff. That keeps planning iteration cleaner than editing multiple external files too early.

4. Risks

Use Risks to review shortage, overbuild, inventory-pressure, or blind-spot concerns before handoff.

The point of this step is not only to list risks, but to make the assumptions and follow-up actions explicit enough for planners and operators to act on them.

5. Compare

Use Compare to review what changed between the current working version and an earlier DashboardGenius version.

This is useful when you need to answer questions like:

• what changed since the last review
• which items moved most
• whether planner adjustments materially changed the plan

6. Export Handoff

Use Export Handoff when the working version is ready to leave DashboardGenius as a planning artifact.

The current product flow supports an Excel-first handoff so the planner or execution owner can take a cleaner output forward.

Before export, confirm:

1. source review is complete
2. planned demand review is complete
3. risks are acknowledged or documented
4. handoff caveats are clear

Working Versions

Demand Planning supports DG-side working versions so your team can iterate without immediately overwriting the original planning inputs.

That is useful when:

• planners want to test alternatives
• the team needs a before-vs-after review
• a working version should stay internal until the handoff is ready

Treat these versions as decision support and review history, not as a substitute for your final execution system.

Best Practices

• Review source health before adjusting the plan.
• Keep planner notes short and decision-oriented.
• Make risks explicit instead of assuming the recipient knows the tradeoff.
• Compare against the prior working version when changes need explanation.
• Record handoff caveats before export so downstream owners do not inherit silent assumptions.

Common Mistakes to Avoid

• skipping source review and going straight to adjustments
• using Demand Planning for one-off exploratory questions that belong in chat
• exporting too early before risks and caveats are documented
• treating the app as a final execution system instead of a planning review surface

Next Guide

Continue with Gallery and Shared Insights.