Information across several places
Records live in spreadsheets, email and separate tools. A focused product can give a defined workflow a clearer source of information.
Services / Vienna
Software shaped
around your work.
HATT brings strategy, product design and engineering together to build focused digital products for operational workflows.
Discuss your projectWhere we can help
When the process
needs a better tool.
Decisions that are hard to follow
People need to see the criteria, current status and next action without rebuilding the context each time.
A repeatable task with changing details
Document creation and operational checks need consistent structure while allowing the values and exceptions to vary.
The approach
From a real process
to a working product.
Understand the process
Follow a real request from its arrival to completion. Identify the information, people and decisions the product needs to support.
Bring an example of the current workflow, including a case that did not go as planned.
Define a useful product
Turn that understanding into a focused scope and an interface people can use. Work through the normal path and the exceptions before committing to the build.
The first version should resolve a defined part of the process, with clear boundaries.
Build around the work
Develop the product around its records, decisions and handoffs. Check how it behaves when information is missing or the process changes.
Review the working product against the task it needs to support, then refine it.
Inside the work
Decisions you
can inspect.
These product stories show our work. Product status is stated on each page; the examples are not claims of client results.
Scout: reusable matching criteria
A profile, version history and explicit results states for grant and tender discovery. Private access.
Asset Inventory: a structured count
Asset records, commissions and discrepancy review in a prototype under development.
Folio: templates and structured rows
A desktop document workflow that generates Word documents from a shared template.
The first conversation
Bring the task
you want to improve.
Describe who does the work, which tools they use and where the process becomes difficult. A sample document or an anonymised workflow example can make the discussion more concrete.
There is no need to arrive with a finished specification. Explain what a useful change would let the team do, and mention any known constraints.
Have a project in mind?