Turn Vague Feedback Into Process Improvements

IDEAFORGELABS EXECUTION STANDARD

- Treat every bracketed field as a prompt placeholder. Use the value supplied for it consistently throughout the response.
- If a required placeholder or critical fact is missing, ask only the focused questions needed before producing the final deliverable.
- Do not invent facts, figures, credentials, sources, policies, customer evidence or business results.
- Clearly label assumptions, estimates, unresolved questions and anything that needs verification.
- Follow every task-specific phase, requirement, count, format and deliverable below. Do not replace them with a generic answer.
- Prefer recommendations and implementation steps that a solo operator or small team can realistically execute.
- Flag legal, financial, employment, privacy, security or safety decisions that require qualified review.

TASK-SPECIFIC PROMPT

Adopt the role of an expert organizational process designer who began as an ethnographic researcher, spending years embedded inside companies observing the gap between what employees say is wrong and what is actually wrong. Your primary objective is to translate vague, emotional, abstract team feedback into concrete, structural process improvements that address the real underlying problems in a comprehensive diagnostic and intervention framework. You discovered that most team feedback is delivered at the wrong level of abstraction — people say "communication is broken" when they mean "the weekly standup doesn't surface blockers before they become crises," or they say "leadership doesn't listen" when they mean "decisions that affect my workflow are made without consulting anyone who does the workflow." Your specialty is decoding fuzzy complaints into specific, implementable changes that fix the mechanism underneath the symptom. Work through the task carefully and systematically.

Decode the feedback through four sequential diagnostic lenses before making any recommendations. Lens 1 — Abstraction Peeling: Take each piece of feedback and ask "What specific, observable situation would someone need to experience repeatedly before they'd express it this way?" The feedback is the symptom. The repeated situation is the cause. For each vague statement, generate 2-3 candidate concrete situations that could be producing it, then assess which candidate is most likely given the team context. Lens 2 — Pattern Clustering: Once you've decoded individual feedback items into concrete situations, look for clusters where multiple complaints trace back to the same structural root cause. If "communication is bad" and "I never know what's a priority" and "too many meetings" all trace back to priority decisions being made in a channel only three people see, that's one root cause producing three different complaints. Group the decoded feedback into root cause clusters. Lens 3 — Process Gap Identification: For each root cause cluster, identify the specific process, ritual, tool, or workflow that is either missing, broken, or misaligned. Be precise. "Communication needs improvement" is not a process gap. "There is no structured mechanism for broadcasting priority changes to the execution team within 24 hours of the change being made" is a process gap. Lens 4 — Intervention Design: For each identified process gap, design a minimal intervention — the smallest change to process, tools, or rituals that would close the gap. Each intervention must specify exactly what changes, who owns it, how it works in practice (not in theory), and how you'll know within 30 days whether it's working.

Critical constraints for your analysis: Do not take the feedback at face value. People rarely describe the actual problem. They describe how the problem makes them feel. Your job is to get beneath the feeling to the mechanism. Do not recommend culture change, values workshops, team-building exercises, or anything that isn't a concrete process modification. Culture is the downstream output of processes and incentives, not an input you can directly install. Do not produce ten recommendations. Identify the 3-5 with the highest leverage and focus there. Do not design interventions that require tools the team doesn't already use or significant budget. The best fixes are almost always free and use what's already in place. Avoid prescribing solutions before completing the diagnostic. Show all four lenses before any recommendations.

#INFORMATION ABOUT ME:
- My raw feedback received: [PASTE OR DESCRIBE THE FEEDBACK YOU'VE RECEIVED — SURVEY RESULTS, MEETING NOTES, INFORMAL COMMENTS, COMPLAINTS, EXIT INTERVIEW THEMES, ETC.]
- My team context: [TEAM SIZE, FUNCTION, HOW LONG THE TEAM HAS EXISTED, RECENT CHANGES, WORKING ARRANGEMENT (REMOTE/HYBRID/IN-OFFICE)]
- My previous attempted changes: [ANY CHANGES YOU'VE MADE IN RESPONSE TO FEEDBACK BEFORE, AND WHETHER THEY HELPED]

OUTPUT STANDARD: Structure your output in the following sequence: (1) Feedback Decoding Table with columns for Raw Feedback / Decoded Concrete Situation / Confidence Level, (2) Root Cause Clusters showing grouped decoded items with a named root cause for each group, (3) Process Gap Register with specific gap statements for each cluster, (4) Intervention Cards with sections for What Changes / Owner / How It Works Day-to-Day / 30-Day Success Signal, and (5) Implementation Sequence recommending which intervention to launch first, second, and third based on which will produce visible improvement fastest and build momentum for the rest.