Start with the progress, not the feature
Find the change a person is trying to make, the forces holding them back, and the language they already use for the problem.
A clear brief for what deserves to exist
Make images that belong to the work
Turn an approved visual direction into illustrations and photographic prompts that carry the same material, tone, and judgement as the rest of the product.
A reusable image recipe instead of isolated decoration
Let people change their mind before the build
Turn the first idea into a sketch, a clickable prototype, or a small working page—only detailed enough to answer the live question.
A cheap thing to react to, before an expensive thing to maintain
Give language the same care as the interface
Write the words that help someone act: the invitation, the setting, the confirmation, the moment when something goes wrong.
Product language that does not leave people guessing
Make a visual system that can travel
Choose type, colour, spacing, and imagery as a shared vocabulary, then make the rules legible to people and to the code.
A design system with a point of view, not a pile of variables
Meet the system you already have
Fit a decided interface to the real components, tokens, and constraints of a project without quietly changing the product to suit a library.
The existing stack becomes a useful boundary, not a design brief
Look at it through someone else’s eyes
Ask different people to read the same page, message, or proposition independently, then pay attention to where their readings converge and split.
A check on whether the work lands beyond the room that made it
Walk the path, not just the screen
Take a real task and attempt it step by step. The important question is not whether the interface looks coherent, but whether someone can finish what they came to do.
A record of where the experience actually breaks
Borrow a point of view
Let an engineer, a sceptical buyer, an operator, or another stakeholder read the work from their own practical concerns before it has to survive a real meeting.
Constructive friction before the cost of commitment
Check the familiar things people still miss
Inspect a screen against the usability principles that make a system feel understandable, reversible, and calm when something unexpected happens.
A disciplined critique of what the interface asks people to carry
Make the layout survive use
Check the structural details that undo good intentions: dense information, small screens, touch, contrast, URLs, loading states, and the awkward edge cases.
A practical guard against polished but brittle interfaces
Stress-test the decisions
Review a design against familiar usability principles, structural failure modes, contrast, and the details that are easy to miss in a beautiful first pass.
Specific shortcomings, with their severity and their evidence
Show the change a person can feel
Describe the before and after in human terms: the tension, the relief, the new capability—not only the output a product happens to produce.
A transformation story strong enough to test against reality
Build a visual voice, then use it
Explore an identity before committing it to rules; when the direction is clear, make illustration and image work that belongs to the same world.
A coherent visual language from first reference to finished asset
Choose type in the product’s own words
Test actual headlines, long reading, dense tables, symbols, weights, and languages before calling a typeface the right one.
A type decision based on use, not a specimen pangram
Find the next move
When the path is unclear, Humane reads the handoffs between its tools so the next step follows the work instead of a generic playbook.
A method that can explain where it is going and why
Prepare the ground
Check what a project can actually use—its context, sources, tools, tokens, and review surfaces—before asking an agent to promise work it cannot verify.
A working environment made explicit before the first decision
Make interaction feel present
Build a small family of tactile sounds for the moments a person can feel: a panel catching, a choice landing, a task completing—quietly, without turning the interface into a game.
A sound palette that belongs to the product, not a layer of noise
