Delivery team
Rebuilding how a delivery team works

When I asked my boss to show me how we were managing projects, he opened a customer’s project plan. Then another page for the next customer. Then another. He knew what was happening across those projects, but we needed a way for the team to see the commitments we were managing and where information was missing.
I built a pipeline that brought the projects into one view, including the dates that hadn’t been filled in. That gave us a starting point. My boss had already built the foundations of our delivery approach, and we worked together to refine how the team managed the work as we brought agents into it.
After customer meetings, delivery leads were piecing together notes and updating our customer and project records by hand. We connected the meeting types to the work expected at each stage of a project, so agents could propose updates and identify tasks to add or close. The delivery lead still had to decide whether those actions served the customer’s goals.
Preparation was another part of the same effort. We built a shared skill that assembled current materials and customer context into a presentation. I designed a lightweight registry for the team’s shared skills, with team leads owning their definitions. The person taking a presentation into a meeting remained responsible for its accuracy and for making it useful to the people in the room. Having a deck ready didn’t mean that work was finished.
Adoption took work too. Some people continued making updates manually, and information the agents knew to capture was still getting missed. Seeing the workflow run for a colleague helped people understand what they could hand over.
As preparation and follow-up took less time, we had more room for customers and for developing the team. Delivery leads could present their work to colleagues and get feedback before taking it into a customer meeting. Senior leads had more time to help them build the judgment they still needed when the agents had finished their part.
What are you automating? follows the meeting workflow. When is the work actually done? looks at preparation, shared skills and the responsibility that stays with the person.
