Include the intended audience
Define the language, hearing, vision and other access needs of the actual experience, then identify appropriate content and delivery methods.
Plan inclusive experiences ↗PUBLIC AGENCIES & CIVIC PROJECTS
Public experiences
built around people.
Public projects need an engaging experience, practical operation and clear accountability for the work delivered. Mad connects design and engineering with multilingual content, accessibility and lifecycle requirements defined for the institution.
WORKING WITH MAD
Turn the public purpose into project requirements.
Plan for staff and maintenance
Specify operator controls, documentation, training, support responsibilities and realistic component refreshes.
Plan for support ↗Make the decisions accountable
Document the options, assumptions and acceptance evidence so the institution can assess what it is buying.
Procurement and evidence ↗PROJECT EVIDENCE
See the specific contribution.
A California DWR exhibition
At the Department of Water Resources’ Vista del Lago Visitor Center, QuickSilver and Alice support a technology exhibition with visitor preferences.
Read the project ↗A presidential library and museum
At the Harry S. Truman Library and Museum in Independence, Missouri, Mad contributed consultancy, design and implementation of audiovisual and interactive equipment for the renewed exhibitions.
Read the project ↗TECHNICAL DETAILDefine data, access and operating responsibilities.
Open the engineering detailClose this sectionLook for the red circuit symbol for engineering detail.
| Decision | What to define |
|---|---|
| Public access | Language and accessibility requirements should be tied to usable visitor experiences and project-specific acceptance tests. |
| Data and privacy | When personalization is included, define anonymous routes, consent, data minimization, retention and authorized access. |
| Governed AI | If AI is in scope, specify source authority, permitted actions, review, fallback and audit requirements. A named framework is an option to evaluate, not a requirement for every project. |
| Lifecycle | Record hardware and software dependencies, licenses, support arrangements and the institution’s access to maintainable documentation. |
Accessibility, privacy, procurement and other requirements are established for the jurisdiction and project. The scope should state what is being designed, what evidence is required and who is responsible for approval.
CAPABILITY AND EVIDENCE
A clear scope for your project.
Connect the public experience to a supportable delivery plan. Accessible and multilingual content, operational responsibilities and long-term care belong in the scope alongside the technology. Any developing capability needs a defined engineering task and a clear acceptance requirement.
LET’S BUILD WHAT COMES NEXT
What does your next decision need?
Tell us the project stage, the people involved and the question you are trying to resolve. We can agree a useful next step.
Start a conversation