🧱 Lemmings — Delegation as design
A crowd of tiny figures, with a few raised above the rest as builders, diggers, and blockers.
🧠 UX Interpretation: Roles instead of direct control
In Lemmings you never pilot a single character. You assign jobs. This one becomes a blocker. That one digs. Another builds a staircase, then returns to marching. Your power lies in choosing who does what and when. You design a tiny organisation on the fly, under time pressure, with no way to stop the clock.
That is close to how complex products work. Interfaces rarely move data themselves. They delegate. Background jobs, services, scripts, and people each hold a piece of the task. UX succeeds when those roles line up cleanly.
🎯 Theme: Orchestration
Lemmings shows that giving a role is very different from giving a command. A builder keeps building. A blocker keeps blocking. Forget to remove them and they become part of the problem. The same applies to permissions and automation. Rules you set once can outlive the situation that made them sensible.
💡 UX Takeaways
- Design clear roles with visible limits and duration.
- Show who is “blocking” and why, whether human or system.
- Make it easy to revoke or change a role without side effects.
- Explain automation in plain language so users know what will happen next.
- Audit long-lived rules. Yesterday’s helper can be today’s bottleneck.
📎 Footnote
Lemmings offered only a handful of jobs, yet the combinations felt endless. That restraint is a lesson. You do not need dozens of permission types. You need a small, legible set that users can reason about at speed. The rest is timing and judgment, which no interface can fully automate.