Keep the source attached.
A statement needs its context: a message, a document or a direct observation. Its source and date help distinguish older information from a new development.
Personal project / Organising digital work
Turning scattered information into a clear next step. A personal project about organising work, using AI and knowing when a case has actually moved forward.
01 / THE STARTING POINT
A message here. A document there. And a question in between: which information is still current?
I wanted to organise recurring administrative work so that I could pick it up later with a clear understanding of the situation. A summary alone isn't enough. It needs to show where the information came from, what has already happened and which questions remain open.
Using ChatGPT and Codex, I developed task briefs, status overviews and handovers. AI helps with analysis, structure and wording. I set the goal and scope, add context and check that the result reflects the actual situation.
The work is divided into individual cases, each with its own context. A compact overall summary keeps priorities and dependencies connected. Documents and results are saved as files so they are available at handover. When new information arrives, it is checked against the existing record. This creates a working foundation that can be continued, instead of an ever-longer collection of separate answers.
02 / THE STRUCTURE
A statement needs its context: a message, a document or a direct observation. Its source and date help distinguish older information from a new development.
Confirmed facts, assumptions and missing information have different levels of certainty. This matters especially when combining several sources.
A general intention becomes an actionable task: what is needed, who needs to contribute and how will we know it is complete?
A draft, an approved action and a verified result are different stages. Text, information and intended actions are checked before they are used.
At the end of a session, the current status, open points and next trigger are clear. The next session can then continue without starting from scratch.
03 / TRY IT YOURSELF
The same information at four stages. This example shows how an enquiry becomes clearer without claiming a solution too soon.
01 / Received
An audio problem has been reported. The message gives a meeting time and confirms working video. The affected device and whether the fault also occurs outside the meeting software are still unknown.
Status: logged · No diagnosis or solution confirmed yet.
04 / WHAT I'VE LEARNED
A good handover also makes clear what we don't yet know.
The project has made me more aware of small distinctions with real consequences: is something only proposed, or already done? Is a reply actually new? Do we need more information before the next action makes sense?
The results include reusable task briefs, document packs and traceable status overviews. I continue to develop them in my everyday work. What interests me most is that the same care is needed in technical support, customer service and administration.
My experience in my own online retail business also shows this connection: a task is only properly handled when its information and next steps fit together.
It's part of the project itself. I brought together content from my documents, developed the design with AI, and reviewed and refined the implementation step by step.
The goal is to make my experience more tangible than a list of skills can. The website is both a result and a work sample, including this look at how it was made.
The next connection
I'd like to bring this way of working to a team and develop it further through real tasks.
Let's talk