Application Design
DTS designs applications with attention to usability, accessibility, and how each application connects into an organization's existing operational systems, following the same continuous operating model used across its ecosystem.
The challenge
An application that is difficult to use, inaccessible to some users, or disconnected from the systems around it can undermine the workflow it was built to support, regardless of how capable its underlying features are.
Who this is for
Organizations that need an application designed around how their users and their existing systems actually work, rather than a generic interface applied after the fact.
Our approach
DTS applies its Capture, Structure, Route, Resolve operating model to application design: usability and accessibility are treated as part of keeping a user's path continuous, not a separate concern layered on afterward.
What you can expect
Typical work in this track includes interface design, usability and accessibility considerations, and design work scoped to fit into an organization's existing systems, scoped to what a specific engagement needs.
How we engage
Engagements begin with understanding the users and systems an application needs to serve, move through scoping and delivery, and continue into support once a system is in use.
Security, accessibility, and operations
DTS designs with the same accessibility principles reflected across this site (see the accessibility statement), and security and compliance requirements are scoped explicitly for each engagement, not assumed.
Frequently asked questions
- Does DTS provide application design as a standalone engagement, or only alongside development?
- Both -- design work can be scoped on its own or as part of a broader custom software engagement.
- Does application design include accessibility review?
- Accessibility is treated as part of the design process itself, following the same principles reflected in this site's own accessibility statement.