Download Team work assignment and more Exercises Finance in PDF only on Docsity!
Chosen Organization
Amazon High velocity, internal disagreement, strong culture, weak cross team coordination at scale. Perfect choice if executed correctly.
1 ️⃣ What the Professor Actually Wants
(Decoded)
This project is not about saying: communication is important teams should collaborate better It is about: diagnosing specific coordination failures showing you understand why authority fails designing concrete collaboration systems , not advice acknowledging trade-offs honestly If your paper sounds like management advice, you lose points. If it sounds like organizational design , you win.
2 ️⃣ High-Level Structure (Follow This Exactly)
Your 5–7 page paper should look like this:
- Collaboration Context
- Diagnosis: Where Collaboration Breaks
- Design Principles
- Proposed Collaboration Mechanisms
- Trade-offs and Limits
- Short Conclusion Your slides mirror this structure but compressed.
3 ️⃣ Team Division (6 People, Clean and MECE)
This is the safest full-marks split.
👤 Person 1 – Collaboration Context Lead
Owns Section A
Responsibilities
Define which teams must collaborate at Amazon Explain why collaboration failure is costly
Content to Cover
Product teams Engineering teams Operations and fulfillment AWS vs retail Corporate functions vs frontline
Key Angle (Critical)
Amazon is optimized for speed within teams , not alignment across teams.
Output
1.5 pages Clear mapping of team types One short real example (Prime, AWS, logistics)
👤 Person 2 – Diagnosis Lead (Structural Failures)
Owns Section B part 1
Responsibilities
👤 Person 4 – Design Principles Lead Owns Section C
Responsibilities
Translate diagnosis into rules of design.
Principles Should Sound Like
Collaboration must not slow velocity Disagreement must surface early Ownership must be explicit at boundaries Escalation must be safe and fast
Rule
No mechanisms here. Only principles.
Output
~1 page 4–6 sharp principles 👤 Person 5 – Collaboration Mechanisms Architect Owns Section D This is the highest-scoring section.
Responsibilities
Design actual systems , such as: Decision ownership matrices Escalation ladders Cross team rituals Shared metrics Boundary roles
Examples That Score High
Weekly cross team decision forum with pre reads Explicit DRIs across teams Mandatory post decision alignment ritual Structured disagreement windows
Warning
Do not say “leaders should communicate more”.
Output
1.5–2 pages Bullet points with explanation 👤 Person 6 – Trade-offs + Conclusion Lead Owns Section E + Conclusion
Responsibilities
Admit what your design does not fix Explain why that is acceptable Close the narrative cleanly
Strong Trade-offs
Slower decisions at boundaries Higher coordination cost Some innovation friction
Why This Scores
Professors reward intellectual honesty , not perfection.
Output
~1 page total
- Conclusion Each person speaks 30–40 seconds. No one disappears.
6 ️⃣ Final Warning (Very Important)
What will lose you points: Generic teamwork language Advice instead of design No trade-offs Sounding like students instead of designers What will win you points: Precision Constraints Realism Clear systems thinking
