Group Project

Who it's for

Student teams of three to six on a coursework project, a capstone, a design build or a consulting project for a real client, with the tutor or course leader who runs the module.

Output

• Two team syntheses and a scored report after every simulation, each with the moment that earned the score and one recommended focus
• A trajectory across every retaken room, and one real team meeting, one real conversation and the final presentation run with the rehearsal behind them
• For the tutor, a Ren summary of each member and the team's pattern once three have finished a room
• Scored against published frameworks: Team-Effectiveness Conditions and OKRs, the RACI Matrix, Participatory Facilitation and Roger Schwarz's Ground Rules, Conflict-Mode Flexibility and High-Stakes Dialogue, and the Minto Pyramid Principle and Aristotelian rhetoric

Program contents

1. Purpose and priorities — Team Alignment
2. Ownership and handoffs — Role Clarity
3. Running decisive meetings — Meeting Facilitation
4. Direct team conversations — Team Conflict
5. Defending the work — Presentation Under Pressure

How the program works

A five-week program for student project teams, assigned by a tutor or course leader, built on Renatus. Two team rooms and three simulation rooms · Five weeks, one room a week · Unlimited attempts · Ongoing for a longer project.

The rooms

Why this program exists

A student team takes on a project with a brief, a deadline and marks riding on it. Every group follows the same arc: nobody agrees what the project is for, roles are assumed, not assigned, one member goes quiet by the second week, and the final presentation is written the night before by whoever is still awake. This program prepares the team through private assessment and rehearsal, run alongside the project itself. Ren puts the same questions to every member on their own, then synthesises the team's answers into one picture of where it agrees and where it only appears to.

What you'll achieve

1. Two team syntheses read together: where the project's priorities agree, who owns what and what nobody owns
2. A scored report after each simulation: the scene as it played, each dimension with the moment that earned its score, and one recommended focus
3. Unlimited attempts on every simulation, each a new scene, scored on the same dimensions and charted across the life of the project
4. A rehearsed run at the meeting, the conversation and the final presentation, each done once with Ren before it's done for real

At a glance

Who it's for

Student teams of three to six on a coursework project, a capstone, a design build or a consulting project for a real client, with one tutor or course leader running the module. The team is not in crisis: it has a brief, a deadline and marks riding on it, and it wants to avoid the arc every group project takes. Every room calibrates to the member's role on the team, so the quietest member and the one who usually chairs are read the same way. It assumes the team already has the brief and knows the deadline; it does not assume the team has ever run a meeting that ended in a decision.

Cadence

5 weeks

1

Purpose and priorities · Team Alignment · Read Priorities & Goals and Alignment Signal; list every version of the top priority

2

Ownership and handoffs · Role Clarity · Read Silently Dropped and Broken Handoffs; draft the roles table

3

Running decisive meetings · Meeting Facilitation · Read Structure and Closure across the team; ask which real meeting this matched

4

Direct team conversations · Team Conflict · Read Directness and Aftercare across the team; check whether the real conversation happened

5

Defending the work · Presentation Under Pressure · Read Lead Argument and Poise; set the final presentation questions

Session by session