myBusinessArchitectmyBusinessArchitectmyBusinessArchitectmyBusinessArchitectA year after the board's approval, the first components went live. On the first morning of the Health Sciences pilot, Fiona stood at the back of the advising centre. One advisor had found a struggling student and scheduled outreach; another stared at a blank career section. The quarterly report showed everything green and said almost nothing about outcomes. This final chapter separates outputs, the results a live service produces and the outcomes for the people it serves; builds a six-step benefits tracking process whose last step names who answers for each benefit after the program closes; shows the architecture being wrong and corrected; and ends at Sandra's quarterly review, where the advising service lead answers for the claim and the board reviews the review.
By the end of this chapter, you'll be able to:
A year after the board's approval, almost three years after the crisis that nearly broke Lakeshore Polytechnic, the first components of the Student Experience Transformation went live.
The data integration platform connected the Student Information System and the Learning Management System, giving for the first time a consolidated view of each student's performance and engagement. The advising platform launched in Health Sciences as a pilot, replacing the personal notes and hallway conversations Tom Beaulieu's advisors had relied on. An early version of the student experience portal, as Chapter 5's soft dependencies allowed, gave students one place to see their progress, advising history and career resources.
Fiona stood at 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 Fiona 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 studio with the north-facing window may have perfect light but inadequate ventilation, because nobody anticipated the artist's solvents. "Works" is not a binary judgment. It is an assessment: what serves the purpose the design intended, what falls short, and what reveals needs the design did not anticipate. And beyond the house, the neighbourhood is changing. 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.