关于
你好,我是Kris。
我先试着 理解.
这是我做交互设计的起点。在规划结构、画面或系统之前,我先理解人、矛盾、脉络,以及真正的阻碍。
HAAM怎么工作
HAAM从零散的现实开始。
信息散落在机构、数据库、人、规则、界面、实体场所,以及很久以前做出的决定里。对多数组织而言,这些碎片带来摩擦:难懂的服务、不相连的系统、难以取得的信息、重复工作,以及难以信任或维护的产品。
在决定要做什么之前,HAAM先研究整个系统。我们厘清各部分的关系、责任在哪里、人们需要理解什么,以及哪些事情必须长期可靠。然后把复杂性整理成清楚、实用、能持续运作的产品、服务与数字基础设施。
我们在设计、技术、研究与组织变革的交会处工作,让底层系统更容易理解、值得信赖,能支持真实生活。
什么是交互设计?
设计系统与人相遇的方式。
交互设计安排系统如何回应、用户如何理解下一步,以及体验如何连续发生。当它运作顺畅,复杂的事会变得清楚,决定更容易,产品也更自然好用。
A quick example
- Milo joined the chat · HAAM team member
- Chat with HAAMSee the work
Meaningful work
Build what culture keeps.
Culturally significant work shapes how people remember, participate, learn, gather, and imagine what comes next. It deserves digital products as rigorous as the best-funded commercial systems.
Meaningful work is rarely the easy brief.
More than one audience
Visitors, staff, artists, funders, researchers, volunteers, and future custodians may all need the same system to work differently.
Value is not only revenue
Success may mean access, trust, participation, preservation, continuity, or a stronger public institution.
The story cannot be flattened
Clarity matters, but so do history, language, place, authorship, and the productive complexity that gives the work meaning.
The product must outlive the project
Campaigns end. Grants close. Teams change. The digital system still has to remain understandable, maintainable, and useful.
Treat meaning as a product requirement.
The mission is not decoration added after the interface works. It changes the information architecture, research, governance, measurement, and technical decisions from the beginning.
- Start with the public value
Define what the work protects, enables, or changes before choosing features or formats.
- Make complexity navigable
Organize deep material without turning it into generic marketing copy or an archive no one can enter.
- Design participation, not just attention
Create clear ways to visit, join, contribute, book, learn, volunteer, or return.
- Measure the right outcomes
Pair analytics with qualitative evidence and institution-specific signals instead of treating conversion as the only truth.
- Build for stewardship
Leave systems, content models, and operating decisions that future teams can understand and continue.
Proof, not posture.
The common thread is not sector or aesthetic. It is responsibility for helping valuable work reach people and remain usable over time.
Design convictions
Good design is opinionated.
A product should have a spine. HAAM& is not neutral about speed, clarity, accessibility, or the way a system should behave when people rely on it.
01 Speed
Be obsessed with speed.
A good product doesn't make you wait. Saving a few seconds from the experience is crucial because every delay breaks trust, focus, and momentum.
02 Product
UX is the product.
Use whatever tools are needed to make the product great: research, writing, interface design, code, automation, analytics, accessibility, operations, and support.
03 Clarity
Clarity beats decoration.
Visual taste matters, but the interface has to explain itself first. People should know where they are, what is possible, and what happens next.
04 Accessibility
Accessibility is quality control.
If the product excludes people, breaks on assistive technology, or depends on perfect conditions, it is unfinished. Accessibility raises the standard for everyone.
05 Systems
Design the messy middle.
Most product value lives between departments, edge cases, content, data, calendars, support, and release decisions. Good design makes that operational reality usable.
06 Taste
Make choices.
Generic products happen when nobody takes responsibility for the experience. A strong product has priorities, constraints, and a clear sense of what it refuses to become.
Help improve this website?
Optional analytics. Google Analytics and Clarity load only if allowed; form, email, and chat content are excluded.