What it is
Leadership Lab invites participants to contribute to leadership research through a multidimensional assessment. The public experience explains the purpose clearly, sets expectations for a short completion time, and emphasizes that results remain private between the participant and researchers.
How the engagement worked
This was a straight build: the client paid for the work up front and owns the product outright. The client designed the research study and the assessment instrument itself. Manley Studios designed and built the whole system around it, end to end, and continues to run and maintain it under a maintenance contract.
What had to be right
Research software has two simultaneous obligations: gather information that is useful to the study and earn enough trust for a participant to provide it thoughtfully. Completion flow, privacy language, data boundaries, and the presentation of results are therefore part of the product architecture, not finishing touches.
The participant needs a clear experience that can be completed without understanding the research machinery behind it. The researchers need consistent responses, reproducible scoring, appropriate access, and confidence that convenience features have not quietly changed the meaning of the data.
Decisions that shaped the product
A modern stack, chosen for speed, held to old obligations. Leadership Lab required getting up to speed quickly with Nuxt, Supabase, and the surrounding ecosystem, which were newer tools for me. The underlying engineering problems were immediately familiar. Software still has to represent information accurately, validate it at the right boundaries, protect sensitive data, recover from incomplete work, and remain understandable when requirements change.
Managed services for the parts that don’t define the product. Managed authentication and a hosted database made many capabilities faster to assemble. They do not decide what the data means, who should be allowed to see it, or what should happen when part of a workflow fails. Those decisions stayed in the design.
Privacy as architecture. Access boundaries were built so that results stay between the participant and the researchers, by construction rather than by policy.
What shipped
- A production web application for participants and researchers
- Translating the research process into a participant experience
- Application and data architecture
- Assessment workflow and result delivery
- Privacy-conscious access boundaries
- Production deployment and ongoing operation under a maintenance contract
What this taught the studio
Modern frameworks and AI don’t solve old problems; they move the boundaries. They remove implementation work, introduce new dependencies, and let a small team deliver much more quickly. Neither one decides what the data means, who may see it, or what should happen when a workflow fails. The responsibility for sound engineering decisions stays exactly where it was in 1998.