Teams | Collaboration | Customer Service | Project Management

Benchmarking for projects: how to measure what matters and close the gap

A project that finishes on time isn't automatically a project that performed well. I've seen plenty of "green status" projects that quietly burned through margin, overloaded the team, and left the client underwhelmed. Without a reference point, you can't tell the difference between a genuinely healthy project and one that just crossed the finish line.

Resource levelling: what it is, how it works, and when to use it

I spent the best part of a decade in client services, and have seen firsthand how resource planning can make or break your team and projects. If there is one thing I have learned, it is that most project delays do not start with bad estimates or unclear scope. They start with a resource plan that looks fine on paper but falls apart the moment two projects need the same person on the same day.

Element recognised as a Digital Public Good

We're pleased that Element has been recognised as a Digital Public Good by the Digital Public Goods Alliance (DPGA), a multi-stakeholder initiative endorsed by the United Nations. To qualify as a Digital Public Good (DPG) a solution must meet a rigorous set of criteria. In particular open licensing, clear ownership, platform independence, strong documentation, privacy compliance and adherence to open standards.

Preserving Retro ROM Hack Showcases With a Twitter Downloader

Retro ROM hack makers drop jaw-dropping showcase clips on X, then pull the posts down once a build changes. A Twitter Downloader keeps those moments reachable. The hack corner of online games runs on momentum. A new patch demo trends for a day, collects replies, and quietly vanishes when the creator reworks the project or deactivates. That fragility is the whole problem. You watch a clever Mario or Zelda overhaul, plan to study the level design later, and the link is dead by the weekend.

10 essential project management reports every team should use

Let’s be honest about how projects usually go sideways. A task gets blocked and nobody notices. A dependency changes and nobody updates the plan. A senior stakeholder says “small tweak” and the team hears “new scope.” A key engineer goes on leave and the work shifts into the future. Then you get that message: “Can we still ship by Friday?” And you don't have an answer, because there is no single space that tells the whole truth.