Gantt feedback — what we were supposed to work on
Purpose: Breakout of the specific Gantt-related feedback from LMNT so we can address it in the actual Gantt (and in the proposal). Use this when updating the Gantt chart and when recording the Loom.
1. Renewal vs. original plan (Jason)
Feedback: “Where is the LMNT renewal project unclear on the Gantt? Is the renewal project additive to the existing project plan?” Jason is crosswalking the first Gantt with the recent one.
What to do:
- In the Gantt: Ensure renewal rows are visibly the continuation and expansion of the original plan (same workstreams, extended through Sep; Option B/C add supply chain). No “new project” framing.
- In the proposal: Done — we added “Renewal vs. original plan (Gantt crosswalk)” with a one-liner that renewal = continuation and expansion; rows align when you crosswalk.
- For the Loom: When you have the Gantt on screen, point to how the original rows map to the renewal rows (same three workstreams, then supply chain if B/C).
2. LMNT internal hire by April (Jason)
Feedback: “Gantt shows expected internal hire by April. Is that feasible? How would a hiring delay impact the team’s ability to deliver by September?”
What to do:
- In the Gantt: If we show an “LMNT internal hire” or “LMNT data person” row, label it clearly as LMNT’s plan, not a Brainforge dependency. Or remove it from the BF Gantt and keep it in LMNT’s own planning only.
- In the proposal: Done — we added “LMNT internal hire (April or later)” with: April is LMNT’s plan; delay doesn’t slow BF delivery; delay only affects LMNT’s maintenance/review after handoff.
- For the Loom: One line: “Your April hire is your plan; our delivery by Sep doesn’t depend on it; a delay only affects your maintenance/review capacity after handoff.”
3. Validate timeline and add buffer (Shivani, Feb 19)
Feedback: Shivani’s high-level timeline: Feb = retail clean tables; March = pilot BI + marketing data; April = eCommerce modeling; April–May = eCommerce; June = omnichannel insights; July = supply side. Ask of Brainforge: Validate this sequence and suggest buffer so she’s not over-committing (e.g. omnichannel in July, supply discovery August). Robert/Uttam to reflect in Gantt.
What to do:
- In the Gantt: Review the month-by-month sequence. If we think omnichannel or supply is aggressive, add buffer (e.g. omnichannel insights in June, supply discovery July, supply data visibility Aug, with a note that July could slip to Aug if needed).
- In the proposal: The “Renewal timeline” table already has June = omnichannel, July = supply chain discovery, Aug = supply chain data visibility. Confirm with Uttam that this has buffer built in or add a one-line disclaimer (e.g. “Buffer: supply milestones may shift by one month if discovery takes longer”).
- For the Loom: If we added buffer, say so: “We’ve built in buffer so you’re not over-committing externally; supply could shift by a month if needed.”
4. NetSuite not in “data” rows (Phil, Feb 19)
Feedback: Phil said don’t put NetSuite in these data rows — that’s separate (NetSuite integration). The data section should focus on analytics side only.
What to do:
- In the Gantt: Ensure no row implies that “data” or “renewal” scope includes NetSuite launch/integration. NetSuite stays in LMNT’s own project plan (e.g. MHI/Andy), not in the Brainforge renewal Gantt rows we present.
- In the proposal: Our timeline table doesn’t mention NetSuite; keep it that way. If the shared Gantt (e.g. Instagantt) has a NetSuite row, move it to a separate section or label it “LMNT / MHI (not Brainforge).”
5. North stars and “when does each part of the business get value” (Shivani, Feb 19)
Feedback: They want to see: what’s ingested when, modeled when, when each part of the business gets value. North stars = (1) good omnichannel view of revenue, (2) supply/demand forecasting; milestones month-by-month for each.
What to do:
- In the Gantt: Where possible, make it clear by when each area gets something usable (e.g. “Finance: wholesale rev rec by X”; “Retail: Phil’s POS report by X”; “Omnichannel: first combined view by June”; “Supply: discovery by July, visibility by Aug”). So the Gantt isn’t only “we do ingestion then modeling” but “commercial gets X by month Y; supply gets Z by month Y.”
- In the proposal: The timeline table already has high-level milestones. If the Gantt has more granular rows, add a short “Who gets what when” or “Value by workstream” note (can live in this doc or in the proposal) so Shivani can report out to the company.
Checklist summary
| # | Gantt feedback | In Gantt | In proposal | For Loom |
|---|---|---|---|---|
| 1 | Renewal = additive; crosswalk clear | Ensure rows show continuation + expansion | Done (crosswalk section) | Point to row mapping |
| 2 | Internal hire April; impact of delay | LMNT’s plan only; no BF dependency | Done (internal hire note) | One line on hire/delay |
| 3 | Validate timeline; add buffer | Review sequence; add buffer if needed | Confirm or add buffer disclaimer | Mention buffer if added |
| 4 | NetSuite out of data rows | No NetSuite in BF renewal rows | Already no NetSuite in timeline | — |
| 5 | North stars; when each part gets value | Rows or labels for “value by workstream / by when” | Optional “value by when” note | Optional: “who gets what when” |
Use this doc when you sit down to edit the actual Gantt chart (e.g. Instagantt) and when prepping the Loom.