An impediment is something slowing or stopping the team that they cannot reasonably remove themselves. An issue is something that has already happened and needs managing. Mixing the two is how you get a 'blocker' column that is really a mood.
Impediments, issues, and things the team should own
An impediment is an obstacle to progress toward the Sprint Goal: a locked environment, a missing decision, a specialist who will not answer, a policy that forbids the only sensible test approach. It is still uncertain in the sense that it might be cleared in time — which is why you treat it with an owner, a next action, and a clock.
An issue has landed. The environment is down. The vendor missed the drop. The decision was 'no.' Promote it. Issues get actions and dates, not a hopeful sticker on the impediment list so the count looks stable. The Scrum Master still helps, but the language matters: you are now recovering, not watching.
Not every complaint is your job. 'This story is unclear' is a refinement problem the Product Owner and Developers can fix today. 'I do not like the coding standard' is a team working agreement. If you collect those, you become a suggestion box with a salary. Take what requires organisational muscle or cross-team coordination. Coach the rest back to the people who can move it before lunch.
Clear it like a professional, not a hero
Surface impediments daily, not in a monthly archaeology session. The Daily Scrum is a detection mechanism; the work of removal happens after. Write the impediment as cause, effect on the Sprint Goal, and the person who can actually spend political capital. 'Waiting on architecture' is a fog. 'If the API contract is not signed by Wednesday, checkout cannot start and the Sprint Goal is false' is a request.
Age them. An impediment that is three days old is a different object from one raised this morning. Publish the age. Organisations that hate being measured on impediment age discover a sudden talent for decisions. Organisations that refuse to measure it will thank you for your 'passion' and change nothing.
Use the smallest force that works. A Slack nudge, then a named owner, then the Product Owner, then the manager who owns the dependency, then the sponsor. Jumping straight to the steering committee because it feels decisive is how you spend credibility you will need later. Waiting forever because you dislike conflict is how the Sprint Goal dies politely.
Organisational impediments are the real job
Many impediments are not tickets. They are a shared 'DevOps' team with a six-week queue, a change-advisory board that meets after your Sprint ends, or a hiring freeze that left you without a tester. These will not yield to a cheerful sticky note. They need a narrative: cost of delay, failed Sprint Goals, and a proposed change to the system.
Do not become the single pipe through which every organisational request must flow. That makes you a bottleneck wearing a helpful expression. Teach the team how to raise a request, who the counterpart is, and what 'done' looks like. You stay on the ones that require rank or that span teams who do not share a manager.
Track patterns. Three Sprints blocked by the same environment is not three impediments. It is one structural defect you should be taking to whoever owns platforms. Repeating heroics is a process smell. If your week is a highlight reel of saves, the system is broken and you are decorating it.
Summary & next steps
Impediments block progress and can still be cleared. Issues have landed. Leave the team what they can fix. Write cause, Sprint Goal impact, and an owner; age the item; escalate with the smallest force that works. Organisational impediments need a cost-of-delay story, not another personal favour.
Next: coaching the team — how self-organisation actually works when nobody reports to you and the Sprint Goal is still real.