Concept
Define purpose, audiences and interactions. Identify the part that needs a prototype or demonstration before the team commits.
Develop the idea ↗EARLY ENGAGEMENT
Give the important
decisions room to develop.
An early conversation can connect the creative ambition with the software, physical interfaces, sound and infrastructure it will need. Mad helps the team define the uncertain parts before they become difficult or expensive to change.
THE FIRST USEFUL OUTPUT
A brief the whole team can work from.
A focused initial engagement can produce an experience and technology requirements brief. It records what people should experience, the operating needs, the proposed approach, the important dependencies and the questions that still need testing.
The brief can support concept development, design coordination, budget options or an RFP. The deliverable and the level of detail are agreed around the decision you need to make.
FROM CONCEPT TO COORDINATION
Bring the right questions to each stage.
Design development
Connect software, media, sound and physical design. Coordinate equipment, power, networking, access and the work of other trades.
Develop the detail ↗Procurement and delivery
Turn the agreed requirements into scope, interfaces, evaluation criteria and commissioning evidence.
Specify the result ↗ALREADY UNDER WAY?
Start from where the project is.
Mad can join after drawings have been issued, during delivery or after a venue opens. The useful first step is to understand the decisions already made, the installed infrastructure and the result you need now.
Earlier involvement often leaves more options. Later involvement calls for an assessment of constraints, priorities and the work required to change them.
If the installation already exists, start by assessing what is worth retaining. A QuickSilver® retrofit replaces the legacy playback and control foundation while suitable displays, projectors, loudspeakers and other peripherals can remain. Selected AV++® capabilities can then be planned on that new foundation.
TECHNICAL DETAILWhat the requirements brief can capture.
Open the engineering detailClose this sectionLook for the red circuit symbol for engineering detail.
- Visitor actions, content behavior and physical outcomes.
- Language and accessibility variants, including how complete each supported experience must be.
- Interface, acoustic, media and control requirements.
- Equipment, power, network, cooling and maintenance access assumptions.
- Privacy, permissions and fallback requirements where recognition or AI is included.
- Prototype questions, acceptance tests and responsibilities for unresolved work.
COMMON QUESTIONS
Keep the engagement useful.
Do we have to use Mad as the integrator?
No. Mad can provide design, consultancy, specification support or technical review as a defined engagement alongside your selected delivery team. Any later role is agreed separately.
What if we only need help with one problem?
A defined interaction, acoustic problem, software requirement or system assessment can be a useful scope. Start by telling us what needs to change.
Can we see the relevant technology?
We can plan a focused Wonderland demonstration around the project. The discussion will distinguish working demonstrations, completed integrations and capabilities still under development or qualification.
LET’S BUILD WHAT COMES NEXT
What needs to be decided next?
Bring the brief, drawing, idea or existing-system question. We can identify the work that will make the decision clearer.
Start a conversation