AlfredLetting a task start with just a title.
Alfred, formerly Jarvis, explores how a planning tool can make it easier to capture unfinished work and return to it without losing context. The product starts with a reliable manual experience.
At a glance
- The problem
- Capturing a task can demand too many decisions before the person has even started.
- My contribution
- Designed quick capture and direct scheduling, prioritizing the manual journey before new integrations.
- The outcome
- Progressed from a local prototype to a private hosted beta with persistent task and scheduling data.
Decide when later.Title → day → time & durationInteraction principle
Earlier local prototype · the current hosted beta is private
The problem & my role
Task capture and scheduling can create more decisions than the task itself. Early feedback also showed that technical completion did not guarantee that the manual planning journey felt clear.
What I owned
I design and develop the product through Figma flows, direct interaction review and working prototypes. I define priorities and behavior, review implementation, and decide which explorations proceed.
- Capture
- Start with a title
- Scheduling
- Day, time and duration
- Delivery
- Private hosted beta
Key design decisions
A task can begin with a title. Category, priority and duration should not become hidden assumptions.
Outcome & reflection
The project progressed from a local prototype to an owner-private hosted beta in October 2026, with persistent task and scheduling data. Ongoing work focuses on usability and dependable everyday behavior.
The image is an earlier local prototype, shown as part of the development story. The beta is private. AI functionality and Google integration remain planned work.
What I would test next
Observe an uncoached user completing capture, edit and scheduling tasks, then refine the points that still require explanation.