BA Brew

The episode surfaces a handful of genuinely practical applications of service frameworks (capability heat-mapping, recruitment gap-filling, cross-profession overlap identification) but is heavily padded with career reminiscence, mutual affirmations, and definitional restatements that reduce the ideas-per-minute ratio significantly.

“we can consider almost like a heat map really, the different LSD offers that we have and how those map to the service framework. And therefore, are there gaps, are there areas where we're not providing the right sort of support”

“we've also used it to help with recruitment you know we were we were light on a certain area and and you know the team that was in place didn't have experience of x so as we've gone to market”

The cross-profession service framework alignment angle - showing BA, business architecture, and service design overlap to enable collaboration rather than turf wars - is a moderately fresh framing, but the underlying advice (reframe conflict as collaboration, define what you don't do, use shared language) is fairly standard professional development fare.

“I'd really rather we reframe some of those role conflicts as opportunities for great collaboration rather than getting into a bit of a turf”

“a service blueprint is only ever written by someone who is a service designer and I think service designers are very well placed to build service blueprints They have expertise But I also think that it a technique”

Both guests are working practitioners with genuine organizational depth - Chris has embedded the framework across multiple large organizations including DWP and presented at the European Conference; Victoria co-authored a book on business architecture and has applied the framework in a scaled enterprise context. They are credible but mid-level practitioners rather than senior transformation leaders.

“currently at DWP, we use a BA service framework and we've adjusted some of the services to fit better the nature of the, many of our BAs are deployed, embedded into agile product delivery teams”

“we've recently revisited it based on the work that me and you have done in the recent publication of Business Architecture Comprehensive Guide”

There are some genuine specifics - DWP named, 120 BAs versus 5 business architects cited, a concrete example of merging two services into 'support and enable solution delivery' - but the episode has no outcome metrics, no dollar figures, no timeline data, and the examples rarely go deep enough to be directly replicable.

“in my organization we have 120 ish business analysts who are embedded in change activity across the organization there are five business architects”

“we amalgamated the the latter two services around acceptance testing and transition and release into something we framed as more support and enable solution delivery, which sort of covers supporting solution creation, acceptance, transition, release, and impact measurement”

The host is knowledgeable about the subject matter but conducts a supportive PR-style chat rather than a probing interview - no claim is challenged, questions are open invitations to expand, and effusive praise ('brilliant brilliant,' 'what an answer that was, I'm very impressed') repeatedly interrupts the flow without adding substance.

“what an answer that was that was a brilliant answer Chris I'm very impressed”

“brilliant brilliant some some brilliant collective advice”