Case Study
Fieldwork is a fictional digital design studio. This concept connects the public introduction to the studio with the everyday experience of collaborating on a project.
Company
Fieldwork
Role
Product Designer
Year
2026

- Project
- Fictional interface concept
- Challenge
- A studio website and client portal built around clear scope, visible progress, and focused feedback.
- Focus
- Information architecture, interaction design, and interface design
- Status
- Concept prototype; no production metrics claimed
The challenge
A persuasive studio website and a useful client workspace solve different problems. The first explains the offering; the second helps a client understand what is happening now. When those experiences feel disconnected, expectations established during the sales conversation can become difficult to track during delivery.
Design approach
I structured the public site around a small set of services and selected projects. Each service explains the problem it addresses, the likely deliverables, and the decisions required from a client. The visual language then carries into a project portal with the same terms and hierarchy.

A clear introduction to the studio offering
A focused interaction
The portal prioritizes milestones and decisions over a long stream of activity. Each milestone has a clear state, an owner, and the next expected contribution. Completed work stays accessible, but does not compete with the item that needs attention today.

Milestones with an explicit next step
The complete experience
Design reviews pair a large preview with contextual feedback. Comments are attached to the relevant version, and approval is a deliberate action with a clear consequence. A request for changes becomes a visible decision rather than an ambiguous message in a separate channel.

Feedback tied to a design version
Concept outcome
The concept creates a consistent journey from understanding the studio to reviewing its work. The project is fictional and has not been launched. Its proposed value is clearer expectations and a more manageable review process, rather than an invented increase in revenue or delivery speed.
Next iteration
The next iteration would explore how the portal handles an overdue decision and a change in scope while keeping the relationship constructive and the project status understandable.