People
We observe behavior in context and listen for what requirements documents leave out.
We study how work really happens in Dhaka, the Gulf, and the EU — then design software that respects it.
Tingeworks is a research-led software design studio based in Dhanmondi, Dhaka. We look closely at the people, routines, constraints, and informal workarounds around a system before deciding what should change.
That perspective comes from anthropology, accessibility, and systems thinking. It helps us find the precise intervention that makes software feel calmer, clearer, and more useful — for a logistics team in Dhaka or a sustainability platform serving the EU.
“The best software disappears behind the work people actually came to do.”
We observe behavior in context and listen for what requirements documents leave out.
We trace dependencies, policies, and edge cases so simpler interfaces do not hide fragile logic.
We treat accessibility, language, performance, and interaction as parts of the same experience.
Every engagement begins the same way: we go and look. Before a single screen is drawn we sit with the people who will use the thing — in their office, on their route, at their counter — and watch what they actually do rather than what a process document says they do.
That gap is where most software fails. A dispatcher keeps a paper notebook beside a ৳40-lakh fleet system because the system cannot record a driver calling in sick. A compliance officer maintains a private spreadsheet because the official report arrives two days too late. These workarounds are not user error. They are the clearest available specification of what the software should have done, and you only find them by being in the room.
Anthropology. Ethnographic method — participant observation, contextual inquiry, thick description — is built for exactly this problem: understanding a practice from the inside rather than from a requirements list.
Accessibility. We design and audit to WCAG 2.2 AA. In practice this makes software better for everyone, not only for users with disabilities: clearer hierarchy, better contrast, keyboard paths that also make power users faster.
Systems thinking. An interface that hides fragile logic is not simple, it is deferred failure. We trace dependencies, policies, and edge cases before we simplify anything.
Organisations running operational software that people depend on daily: logistics and fleet operations, ESG and supply-chain analytics, specialised education, real estate and interiors. The common thread is complexity that cannot be designed away, only designed for.
We work with clients in Bangladesh, across the Gulf, and in the European Union. For EU clients we handle research data under GDPR — see our Privacy Policy for how participant data is treated.
If you want to see the method applied, read the case studies. If you know what you need, the UX research and product design pages set out how each engagement runs. Otherwise, tell us what is not working.
In Dhanmondi, Dhaka. Our researchers work on site with clients across Bangladesh and remotely with teams in the Gulf and the European Union.
The order of operations. A research-led studio establishes what is actually happening — through observation, interviews, and data — before proposing an interface. Most studios begin with a visual concept and validate it afterwards, if at all.
Yes. We work with clients across the Gulf and the European Union, and handle personal data under GDPR where EU residents are involved.