02 / Procurement · Solution architecture
When decisions no longer have to wait for the next meeting.
A procurement process relied on committees meeting twice a month. I helped design a SharePoint portal to bring this workflow into the environment the operations team already used.
How can decisions move beyond meeting dates while preserving their rules?
01 / Starting point
Understand the decision before designing the screen.
Discovery brought together documentation, process records, the operations team and a procurement specialist. Fixed meeting dates shaped how requests moved forward.
Translating this into software required understanding who made decisions, what information they needed and which rules had to remain in place.
02 / My contribution
Architecture and permissions were part of the product.
My responsibility focused on architecture and security requirements: authentication, permissions and vote visibility. These choices determined what each participant could do and see.
We used SharePoint, which was already part of the client's environment. A two-person team built the proof of concept, working across business and development.
03 / How we built it
Make the workflow specific enough to implement.
AI supported the preparation of requirements, specifications, documentation and tests. The team remained responsible for clarifying rules and validating behaviour.
The case connects process design with architecture: the user experience needed to reflect decision rules, including information that should not be visible to everyone.