Raf Sanga dot com

A lightweight decision log preserves the outcome, reason, owner and review trigger so teams can move forward without repeating the same discussion. You leave a meeting with a clear decision. Two weeks later, the same topic appears again in another meeting. Someone missed the context. Someone else remembers a different version. A new stakeholder asks why the option was rejected. Suddenly the team is not progressing the work. It is reopening the past. This is one of the quiet ways projects lose time. Most teams do not suffer from a lack of decisions. They suffer from decisions that disappear into meeting notes, emails, chat threads, slide decks and people’s memory. When that happens, every change in stakeholder, priority or pressure creates an opportunity to relitigate something that was already resolved. A decision log is a simple way to stop that drift. Not a bureaucracy. Not a governance artefact for its own sake. A lightweight record of what was decided, why it wa...

A simple intake system makes workplace trade-offs visible before every request becomes urgent. A team has twelve active projects, a full improvement backlog and several deadlines already at risk. Then another request arrives marked “urgent”. It sounds important. A senior stakeholder is asking. The email mentions a meeting next week. Nobody wants to appear unhelpful, so the team starts immediately. Two days later, a genuinely time-critical request appears. Work stops again. The original task joins several half-finished items, while the team spends more time switching priorities than delivering them. The problem is not a lack of effort. It is the absence of a shared intake and prioritisation system. Why this matters When work arrives through emails, meetings, chat messages and corridor conversations, the queue becomes invisible. The loudest requester can receive attention before the most valuable work. People accept more than the team can finish because every request i...

Before selecting automation, make the real workflow visible enough for the team to improve it. A team is frustrated by a slow approval process. Emails are missed, documents are returned for correction and nobody can say exactly where requests are sitting. The proposed solution arrives quickly: buy a workflow tool, build an automated form or add AI. That may help. But there is a catch. If the team has not agreed on how the work happens today, automation can make the confusion move faster. An unnecessary approval becomes an automated unnecessary approval. Poor information reaches the next person sooner. Exceptions that used to be handled through a quick conversation become system errors. Before choosing the technology, map the work. Why This Matters Most workplace processes are less tidy than their procedure documents suggest. Over time, people add checks, spreadsheets, workarounds and informal handoffs. Each addition may have made sense at the time, but the whole proce...

AI can help structure messy updates, but the final status report still needs evidence, judgement and human approval. A project can have plenty of updates and still leave leaders unsure about what is happening. One person reports that testing is “nearly complete”. Another says a dependency is “being worked through”. The project plan shows a milestone in two weeks, while the meeting notes mention a delay that has not reached the risk register. By Friday, the project manager has several versions of the truth and a blank status-report template. This is a good use for workplace AI, but only if AI is treated as a drafting assistant, not the owner of the project story. The aim is not to make reporting sound more polished. It is to turn scattered evidence into a short, decision-ready update that a responsible person checks and approves. Why This Problem Matters A status report should help its audience understand the project’s position and act where needed. Public project-stat...

A simple project-brief structure can make workplace AI outputs clearer, safer and easier to review. You open an AI tool between meetings and type something like, “Summarise this,” “Write a project plan,” or “Help me improve this process.” The answer arrives quickly. It sounds polished. It may even be useful. But it is also a bit too broad, a bit too confident, and not quite grounded in the messy reality of your workplace. That is where many people get stuck. They treat AI like a search box or a very enthusiastic assistant, then feel disappointed when the output is generic. The better approach is simpler: use AI like you would brief a project team member. A good project brief explains the goal, context, constraints, source material and expected output. The same habit works well with AI. You do not need technical language. You need a clear working brief. Why This Matters AI is already moving into everyday knowledge work: meeting notes, project updates, service improvement...