myBusinessArchitectmyBusinessArchitectmyBusinessArchitectmyBusinessArchitectTwenty-two months after the crisis, the first components of the Student Experience Transformation went live. On the first morning of the Health Sciences pilot, Marcus stood in the back of the advising centre. One advisor had already found a student whose engagement patterns suggested she was struggling and had scheduled a proactive outreach meeting. Another was frustrated: the career services data was not yet integrated, so the career preparation section of the student profile showed a blank screen. Both reactions told Marcus something the architecture needed to hear. The quarterly progress report from Nadia's team showed everything tracking green. It was full of outputs. It said almost nothing about outcomes. This final chapter is about that distinction -- and the full loop it demands: outputs versus outcomes, how delivery experience feeds back into architecture, and how the Design4 cycle begins again when the clients move in, the neighbourhood keeps changing, and the only question that matters is whether what was built is delivering the value the strategy required.
By the end of this chapter, you'll be able to:
Twenty-two months after the crisis that nearly broke Lakeshore Polytechnic, the first component of the Student Experience Transformation went live.
The data integration platform connected the Student Information System and the Learning Management System, producing for the first time a consolidated view of student academic performance and engagement patterns. The advising platform launched in Health Sciences as a pilot, giving Tom Beaulieu's faculty access to structured advising tools that replaced the informal relationship tracking they had been managing through personal notes and hallway conversations. The student experience portal provided a single entry point where students could see their academic progress, advising history, and career preparation resources in one place.
Marcus stood in the back of the Health Sciences advising centre on the first morning of the pilot. Two advisors were using the new platform. One had already found a student whose engagement patterns suggested they were struggling, and she had scheduled a proactive outreach meeting. The other was frustrated: the career services data was not yet integrated, so the "career preparation" section of the student profile showed a blank screen with a message that said "Coming soon."
Both reactions told Marcus something the architecture needed to hear.
The building architect's work does not end when the clients move in. It begins a new phase. The kitchen that looked perfect in the drawings may have the refrigerator door opening into the dishwasher. The studio with the north-facing window may have perfect light but inadequate ventilation, because nobody anticipated the solvents the artist would use. The house works or it does not. But "works" is not a binary judgment. It is a nuanced assessment: what serves the purpose the design intended, what falls short, and what reveals needs the design did not anticipate.
And beyond the house itself, the neighbourhood is changing. New families are moving in. The zoning is shifting. The client's children are growing, and the playroom will need to become a study. The architect's work is never finished because the context never stops evolving.
This chapter is about that assessment and that evolution. Not just "did the initiative deliver value?" but the larger question that the Design4 adaptive learning cycle demands: how does what we learned during delivery reshape what we discover, define, develop, and deliver next?
Create a free account to access Shaping What Gets Built and start learning.