Pitch: The "Anti-Nag" Stakeholder Hub
Appetite: 2-3 Hours (High-Fidelity Prototype)
Driver: Robin (Lead Consultant)
Target User: Philipp (to review) & Robin (to use)
🧐 The Problem
The consultants are being "squeezed like lemons." A typical Lead Consultant manages ~11 stakeholders (9 client-side, 2 internal) who constantly demand progress updates.
Currently, Robin spends high-value hours translating "work done" into "status reports." Worse, the current Tekkr app seems to "punish" him:
- It doesn't track "Ghost Tasks" (ad-hoc client requests), so the project always looks behind schedule.
- Automated meeting transcripts are 30 pages long but contain only 2 lines of actual decisions.
- Clients call at "3 AM" (still don’t know if this is an eggageration or a true story) because they don't have a live view of the truth.
👨🏼💻The Solution
We can try to vibe-build (sigh) a self-updating Stakeholder Hub. Instead of a static project management tool, the hub helps Robin turn chaotic data into clear updates that Robin could use later on in his communication.
The prototype demonstrates this through “control” and “chaos” groups:
- Project A: "Daniel's Interview" (The Control Group)
- Status: ✅ Completed / Green.
- Purpose: Demonstrates the "Happy Path." It serves as the context layer, housing the CV, transcripts, and logs of this interview process, proving organized execution.
- Project B: "UniCorp Series B" (The Stress Test)
- Status: 🟢 On Track → 🚨 Critical Risk.
- Purpose: Demonstrates the "Messy Reality." This is where we stress-test the AI against the "Paris Riot" transcript to prove it can catch "Ghost Tasks" that human PMs miss.
🛠️ The Core Workflow (UniCorp Demo)
1. The Input (The "Pulse" Tab)
- Robin pastes a raw transcript (or uploads a
.txt file) into the project pulse stream.
- Demo Scenario: We use the "Viktor/Robin" transcript where a critical bug is revealed in the final minutes.
2. The Hybrid AI Engine (The Brain)
We implemented a Hybrid Architecture to balance reliability with reality:
- Path A (The Safety Net): A hard-coded trigger detects the specific "Paris/Sentiment" crisis scenario to ensure a flawless, instant demo of the UX vision.