Feedback
The simple question
Does this data product work for your capability?
YES — Done. No action needed.
NO — Describe: What doesn't work? Where is it noticed?
A NO creates a ticket to the product owner.
Why this works
| Principle | Effect |
|---|---|
| System connection only on problem | No unnecessary registration work |
| Free text + context on NO | Owner understands WHAT needs fixing |
| "Bug" in backlog | Concrete, actionable, traceable |
| Silence = approved | Scales to 15,000 employees |
Process
- Capability owner receives a periodic check (bi-weekly or monthly)
- If everything works — no action needed
- If something doesn't work — describe the problem
- Product owner receives the feedback as a ticket
- Product owner fixes or escalates
- Resolution is tracked in the Product Owner Forum
Schedule
| When | What |
|---|---|
| May 2026 | First feedback round (dry run) |
| May–June 2026 | Ongoing feedback collection |
| Bi-weekly | Product Owner Forum reviews open tickets |