Alp ImamogluIssue & action management
Know who is handling an issue, what needs to happen next and when it is due.
These are independent prototypes, not commissioned client implementations. People, companies and figures in the demos are illustrative.
What problem does it address?
An issue gets discussed in an email, then in a meeting. Without a clear owner and a follow-up date, it is still on the agenda a week later.
What did I build?
This prototype brings issues, owners, priorities and follow-up dates together. It gives the team a shared view of the work, without having to ask everyone for an update.
What is in the prototype?
- Create issues and assign an owner
- Track priorities, progress and workload
- Review team skills and weekly work
- Prepare updates and review the change history
What would we measure in a pilot?
In a pilot, I would look at time to assign an owner, overdue work and time spent preparing updates.
Adapting it to your company’s systems
It can be developed to work with a company’s ticketing, email or project tools. Issue types, approval steps and notification rules would follow the way the team actually works.
- Task and issue types
- Ownership and approvals
- Priority rules
- Notifications and reports
The public demos are not connected to live company systems. Integrations and automated notifications are separate parts of a real implementation.
Try the working example
The demo uses illustrative information. Do not enter company or customer data.
Related articles
To improve a workflow, first make the waiting visible
A deadline tells you when work should finish. It does not tell you what is holding it up, who needs to act or which decision comes next.
Five questions I ask before automating a process
Not every repetitive task needs AI. I start with the problem, the information behind it and the consequences of getting it wrong.