Karl Philipp Nolte · Workflows & AI
Clarity before your team gets to work.
What is already known? What is missing? And who decides? Three fictional briefs show how to make a project start reviewable.
Explore the work sampleNo signup. No client data to enter.
Explore and trace
From the input to a shared decision.
Fictional example · Pre-labelled notes · Your selection stays in your browser
How the request arrives.
- N1
Our fictional design studio needs a service page. Visitors should understand the service and be able to request a conversation.
- N2
One German-language page covering the service, process and a contact link. We supply the text and images. An online shop is outside the scope.
- N3
The first draft is due on 15 October 2026.
- N4
The client-side project lead reviews the copy, images and draft before publication.
- N5
The contact link must be easy to reach on a phone. The page must be usable with a keyboard.
A project start you can review.
The information is present. Human review is still required.
- Purpose
Our fictional design studio needs a service page. Visitors should understand the service and be able to request a conversation. N1 ↗
- Deliverable
One German-language page covering the service, process and a contact link. We supply the text and images. An online shop is outside the scope. N2 ↗
- Deadline
The first draft is due on 15 October 2026. N3 ↗
- Responsible reviewer
The client-side project lead reviews the copy, images and draft before publication. N4 ↗
- Acceptance points from the brief
The contact link must be easy to reach on a phone. The page must be usable with a keyboard. N5 ↗
A person confirms the scope, acceptance points and deadline. Only then can the next step be agreed.
What this example actually does
The notes have already been assigned to fields for this demonstration. A fixed rule groups them, flags missing fields and leaves multiple statements open for reconciliation. References N1–N6 lead back to the input. This example does not extract arbitrary client text or call an AI model.
A real workflow would need an agreed input format, required fields, any AI assistance and human review, tested on approved examples. This demonstration does not establish time savings.
A bounded first step
Making it work for your team.
Choose one handover
We clarify which recurring handover causes friction, who uses it and what they need next.
Test a few examples
Using approved examples, we define the input, output template and human review. Only then do we decide whether and where AI would help.
Assess the value together
We compare preparation, review and rework with the existing process. You receive a clear handover; scope and price are agreed in advance.
Discuss your workflow
Where do questions keep coming back?
A few sentences about the process and recurring difficulty are enough for a first message. Please leave confidential briefs and client data out.