關於
你好,我是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.