Ep. 12 - Ten Things I've Learned

Episode 12 of the What's Your Baseline? Enterprise Architecture & Business Process Management Demystified podcast, hosted by Roland Woldt / J-M Erlendson, titled "Ep. 12 - Ten Things I've Learned" was published on December 13, 2021 and runs 51 minutes.

December 13, 2021 ·51m · What's Your Baseline? Enterprise Architecture & Business Process Management Demystified

0:00 / 0:00

Summary

Here it is - the end (of season 1 ... no worries, we're back in January 2022). In this episode we are mixing up the format a bit and are talking about the 10 things that we learned in 25 years of  architecture and process management. Approach / strategy segment Let's talk about the bigger picture, the why and larger setup. What are the thoughts that get organizations started? Why: You’ll end up paying for it somehow. End of the line in people or risk. Don't do a "big effort upfront" Develop and create in releases / have a release plan Processes and architectures need to be measured Organizational segment Architectures win and fail with the people. If they don't want to cooperate or be involved you will fail. It's the people, stupid Do not separate areas of your architecture into different groups Risk & Controls folks are your friends "How-to" segment Once you get started the task of developing an architecture seems daunting. This segment has a few tips to make it more manageable. Start small but don't settle on the lowest denominator - choose a tool and have a minimum set of artifact requirements Have the full lifecycle in mind and don't get distracted by the latest tech When developing models do this in multiple iterations (esp. processes) Please reach out to us by either sending an email to [email protected] or leaving us a voice message by clicking here. The  full show notes, including graphics, further links, credits, and transcript, are available at whatsyourbaseline.com/episode12.

Episode Description

Approach / strategy segment

Let's talk about the bigger picture, the why and larger setup. What are the thoughts that get organizations started?

Why: You’ll end up paying for it somehow. End of the line in people or risk.
Don't do a "big effort upfront"
Develop and create in releases / have a release plan
Processes and architectures need to be measured

Organizational segment

Architectures win and fail with the people. If they don't want to cooperate or be involved you will fail.

It's the people, stupid
Do not separate areas of your architecture into different groups
Risk & Controls folks are your friends

"How-to" segment

Once you get started the task of developing an architecture seems daunting. This segment has a few tips to make it more manageable.

Start small but don't settle on the lowest denominator - choose a tool and have a minimum set of artifact requirements
Have the full lifecycle in mind and don't get distracted by the latest tech
When developing models do this in multiple iterations (esp. processes)

Please reach out to us by either sending an email to [email protected] or leaving us a voice message by clicking here.

The full show notes, including graphics, further links, credits, and transcript, are available at whatsyourbaseline.com/episode12.