After sharing insights into how enterprise architecture can create increased value , align Business and IT , and enable Agile teams to go faster , let’s explore another topic that our thought leaders discussed on our recent webinar entitled, “Modernizing the Role of Enterprise Architecture in the Age of Digital Disruption.” Executive Strategic Advisor John Varicchio , KPMG Enterprise Architecture Leader Roland Woldt , and MEGA’s own Chief Strategy Officer Dan Hebda , closed out their conversation with a robust discussion on how enterprise architecture helps companies to manage risk.
Healthy friction: staying - in-business vs. out-of-trouble
Roland starts the conversation with, “ There’s a big disconnect between the risk organization and the B usiness. O ne group has the idea to keep the organization out - of - trouble while the other group has more of a focus of staying - in - business and that’s an inherent conflict. ”
Dan adds, “I like the notion of separation with stay out - of - trouble versus stay - in - business, which is Gartner’s integrated risk management model. The risk practice has moved from exclusively focusing on staying out - of - trouble to also participating in the stay - in - business side and that’s where you see a smart, strong interaction between risk and enterprise architecture. Obviously, enterprise architecture, is very focused on staying - in - business.
Further, he adds, “ When we speak to moving enterprise architecture towards influential, here's an opportunity for those who may be stuck in noisy, or maybe they’re trying to build some trust from useful, that they can look to establish context . Using architectures, process, and technology can give context to risk and help the Business to generally understand what the effect is on a particular risk and whether or not the proposed mitigations would actually have the effects that we anticipate.”
Disconnected sources create gaps in many Governance Risk and Compliance tools
Roland responds, “When I look at GRC ( G overnance Risk and Compliance) tools, they’re typically some database-driven tools , good looking but not very intuitive, and the one thing that we notice is that users really like to have a process. I see a lot of clients frustrated because they have disconnected sources using multiple policy and risk tools that are not integrated. They need a centered tool in their overall tool stack that allows them to create the inter-connected visualization. This is where I see a gap in many GRC tools.”
Enterprise Architecture tools can create contextualization and allow companies to connect their data, process, and technology to identify, prioritize and mitigate risks. Companies that use MEGA’s Integrated Risk Management solution get a 360 - degree view of risks and business operations. Understanding context allows a company to better qualify and quantify the impact of risks and prioritize mitigation strategies.
Enterprise architecture allows you to accelerate around the bend
Closing out this topic, John reiterates that , “E nterprise architecture can provide the guidance and guardrails to make the organization to go faster . Why does a car have brakes? Because it allows you to go faster , ” John concludes. “ It keeps us out of the ditches and allows us to go fast and accelerate at the bend.”
For additional insights, please view our short videos on how to move your Enterprise Architecture efforts from noisy to influential .
... View more
After sharing the discussion on t he evolution and perceived value of e nterprise a rchitecture and the ability for EA to align Business and Technology , let’s explore what our thought leaders, President of JV Strategic Solutions John Varricchio, KPMG Enterprise Architecture Leader Roland Woldt, and MEGA’s own Chief Strategy Officer Dan Hebda, discussed around how enterprise architecture can fuel business agility during a webinar entitled, “Modernizing the Role of Enterprise Architecture in the Age of Digital Disruption.”
How can e nterprise a rchitecture help stakeholders invest in new technologies and modernize their IT?
John starts off by saying, “Business agility is a strategic necessity for many, many organizations. You look at the pace of change that our clients are faced with where the average lifespan of a company on the S&P 500 is about 15 years down from over 65. A lot of our clients are forced to move faster, clarify the direction, and many of our organizations spend time on modernizing their IT infrastructure and IT environments to become more competitive and prepare for the future. How can the EA group help their stakeholders pivoting to new technologies, modernizing their IT environments, and adding value in this area?”
On-time and on-budget, but is the project still on-strategy?
Dan says , “ One of the things that I think is very interesting and is a ‘ great landing, wrong airport ’ analogy , is that we’ve seen a number of projects where the timeline was wrong. It starts when s omeone has a strategic notion from the executive level, and it gets broken down and decomposed and eventually ends up as a series of projects. Those projects end up hyper - focused on deploying , designing, or developing new technology and within that project execution , they successfully deploy on-time and under budget . Bu t did they check to see if what they actually deployed matches the original strategic expectation? ” To rectify this, Dan notes, “O ne of the things we like to do is use capabilit ies and architecture to establish guidelines or guardrails, and ke ep the awareness as to what the expected outcome is - not just at the technological level but at the business level as well . ”
Instead of saying “No , ” enterprise architects should say “Here’s How”
Continuing the conversation, John says, “One thing we see these days, is that folks don’t want to add an Enterprise Architecture overlay on top of an agile program because it may inhibit the overall speed and agility of the Agile teams. What’s been your experience around how Enterprise Architecture can yield more effectively with Agile project teams?”
“I think the more Agility comes into play, the more enterprise architects need to be directly involved in the project instead of being separate ,” says Dan. “ Architects should be l oan ed out to participate directly i n project executions so that their skin is in the game and they’re part of the team that’s achieving the outcome. In this light, enterprise architecture is not seen as separate and adding some unnecessary burden but rather, EA is seen as someone that can help the Agile teams . So instead of saying ‘no,’ EA says, ‘here’s how,’ and helps the Agile teams to navigate the guardrails, helping them to avoid pitfalls, all the while not slowing the project down and working towards a more likely successful outcome . I think it’s very, very important for the architects to recognize the importance of not being defensive but to recognize that they have to be very cognizant of not slowing the progress down. ”
Embedding enterprise architects into Agile teams helps projects go faster
“ That raises the interesting question ,” says Roland, “W hether you put the architect role on the organizational charts or to be a little bit provocative, do you need enterprise architect s embedded in the project and they report to their product owner? That’s an interesting question that obviously needs to somehow be answered. ”
John raises another point, “ Th is notion of return on teams where teams become more productive the more they work together. The architects work with the project teams and that becomes more of an efficient process. ”
Roland responds, “There is a typical misconception of people thinking that if they go Agile that means they don't have to document stuff. I think that's not true and that was never true.”
John adds to this point, “ It’s a dual problem – how do I modernize and how do I move fast. There was a client I worked with that was spending over 70% of their IT budget just keeping the lights on and wanted to free up budgetary dollars to be more innovative . But to get there, we had to shrink and rationalize the technology footprint and decommission applications to free up budgetary dollars and enable the company to pivot . T he architecture team was invaluable in helping this organization pivot to a new world of innovation and even identify cool disruptive technologies . All the while this company was modernizing infrastructure and moving faster with more Agile methods. It’s kind of like a twin axle on that one. ”
John finishes the point, “So application rationalization is really becoming more a continuous planning process not just a one and done. One really has to continually slice it again because applications become outdated as you modernize.”
For additional insights, please read The Open Group’s “Agile Architecture in the Digital Age,” coauthored by MEGA’s Chief Research and Innovation Officer, Antoine Lonjon
... View more
After sharing the discussion on the evolution and perceived value of enterprise architecture, let’s explore what our thought leaders, President ofJV Strategic Solutions John Varricchio, KPMG Enterprise Architecture Leader Roland Woldt, and MEGA’s own Chief Strategy Officer Dan Hebda, discussed around how enterprise architecture can help align business and technology during a webinar entitled, “Modernizing the Role of Enterprise Architecture in the Age of Digital Disruption.”
How engaged are enterprise architects with the Business today?
In our webinar poll, we learned that 6% of respondents said they do not engage with the Business at all; 24% rarely; 42% occasionally; and 27% regularly. This means that 72% of respondents do not engage with the Business on a regular basis. This is no surprise given enterprise architects tend to work seperately from the Business in their own organization and thus are disconnected from on-the-ground projects. However, in this highly disruptive, agile environment, companies will benefit from a more connected enterprise architecture function to facilitate digital business transformation.
What can enterprise architecture do to help bring the Business and IT closer together?
Dan starts by saying, “One of the things to recognize is that business and IT shouldn’t be treated as two competing aspects. We’re all the same organization. We should have the same aspiration which is to achieve the outcomes defined by the strategy and have an architectural vision to clarify that and bring that together is valuable. Articulating a singular perspective on the strategies that can be viewed through the business or IT lens so that we can then flesh out more specific tactics for each group is very important.”
“I go back to my affinity for business architecture as a piece of enterprise architecture and when it comes to business IT alignment, I think that capabilities are a great way to assess and understand the general gaps in the performance of the organization whether they be business-oriented or technological in nature. Solicit ideas for example on ways of enhancing and improving them and then put that into action. If it’s IT in nature, flesh out the architecture, understand the cause and implications before major investments are made and similarly do the same if it’s Business. Architect or design a mockup of what the processes might look like and the data and technology required to support it, all in advance of the cost. So I think there’s a lot that can be done there.”
Roland agrees, “I’d like to stress what you said. There shouldn’t be two strategies. There should be just one strategy. You can only have one North Star and given the fact that everything is faster we say, ‘Okay, how do we provide technology and business services faster in a more integrated way?’ I see that going on and it doesn’t work with two separate strategies. So mind you, there are some narrow teams in all areas of the organization using Agile versus Waterfall where you have the handoffs and one thing that I really like is the one-stop shop.” Further, Roland adds, “I think three organizations: strategy, architecture and product management, should go together into one - it should be a one-stop shop, one organization that manages the transformation, the change in the organization.”
John Varricchio responds, “Alignment is an area where the Enterprise Architecture group can really step in and lean into and be the first responders to alert the organization that there is misalignment.” Roland agrees, “Enterprise Architecture should be in the KNOW and they should understand how things are wired up. They should be able to run the analysis that’s needed to make the right decisions fast and they should have the tools to be able to not only capture and analyze the thoughts and then rationalize it.”
“I worked with a client where there was a lot of internal frustration around the IT organization, but the IT organization was delivering on all of their commitments. Great project delivery, great results, but the business didn’t care,” adds John. “So it was almost like, ‘great landing, wrong airport,’ so we got the business and IT folks together and it turned out there were actually two strategies: Business strategy and IT strategy. We worked together to unify those strategies, so they had one and their alignment problem was greatly improved.”
For additional insights, please view our short videos on how to move your enterprise architecture efforts from noisy to influential.
... View more
This momentum for business architecture is encouraging. It is being adopted across many organizations, industries and geographies. More business architects are beginning to work with leaders within the business to develop concise views of the business - and because of this reporting structure, they can architect the business and directly apply it. Further, industry reference models created by The Business Architecture Guild are helping to accelerate the application of business architecture because there is little standardization that needs to be established.
Whynde Kuehn, Founder and Managing Partner of S2E Transformation, says, “Business architects should challenge themselves to be not only architects, but also leaders and change agents – and develop value-added skills that complement the business architect role.”
Now, let’s dive into three smart strategies to boost your business architecture efforts:
Strategy #1: Obtain executive sponsorship and share meaningful progress with stakeholders
Business architecture is a journey that is constantly evolving and maturing – as is your organization. If your business architecture efforts started small and built over time or business architecture at your organization was initiated from up above to manage digital transformation efforts, executive sponsorship is key to ensuring credible introductions across the business and providing incentive for people to work with you. In short, if you haven’t obtained executive sponsorship, it’s not too late. Reach out to your supervisor, CIO, or even COO to garner their support.
Sharing business architecture’s value is another important element that is easy, given the very output of business architecture is traceability. Architecture gives traceability at an enterprise level which is imperative now more than ever as organizations grow at rapid pace and as everybody is working in agile environments, with less governance and increased time to market. Business architecture breaks strategies down into objectives, objectives into initiatives or projects, maps them to capabilities which are used in value streams, and then tracked to people, process, and technology. At its very core, business architecture shows how projects and sprints tie back to the bigger picture of the enterprise transformation and show the impact of this enterprise transformation on the capabilities. Thinking about initiatives enhancing the business capability, business architecture switches the mindset of funding a project to funding a new capability, thereby allowing business leaders to better understand where funding is used and can then tie it back to the long-term objectives and vision of the organization.
Lastly, when sharing the progress of your efforts, make sure to take the extra step to think like an executive and communicate to them in their language by connecting the changes to improvements in profitability, efficiency, and cost management.
Strategy #2: Be the connector between the Business and IT
Simply stated, the Business owns the blueprints for the strategic direction and vision of the company, and business architecture supplements this by owning the architectural vision and recommending how to translate their ideas into action. To maximize this, it’s imperative for business architects to go into the business units, understand how they work and interact with customers to design it in architectural terms. This will not only help boost your business architecture efforts, it will also build your credibility as your work will be more complete and accurate.
Further, team up with your fellow architects to show a more robust approach to business value. Enterprise Architects, IT Architects, Solution Architects, and Data Architects need Business Architects and vice versa. For example, business architecture needs to understand customer journeys so they can understand what changes will impact key decision points. To do this, it’s vital to connect with IT and Solution Architects to understand the integration. Further, if a company wants to make a change to its business model (e.g. merger & acquisition, expansion, or new solution), business architecture needs to work together with IT and Enterprise Architects to understand the enterprise view and technology components. Be the connector and your entire team will be recognized for greater value.
Strategy #3: Enable “what if” scenario modeling and bridge the strategy-to-execution gap
It’s important to consider how the relationship between IT and the Business changes and adjusts as organizations introduce Agile methodology and Lean approaches. When business architecture completes current state models, the full value of business architecture comes to bear and “what-if” scenario modeling can be instantly created with greater detail and accuracy. The shorter the ability to understand the impact of “what-if” scenario modeling, the faster a company can get feedback, analyze it and incorporate it. Business architecture plays a critical role in connecting the impact of decisions in people, process, and technology, thereby bridging the strategy-to-execution gap.
Putting this into action, companies are making important decisions everyday whether to expand, introduce a new product, merge or acquire a new company, reduce costs, increase risk resiliency, the list goes on. Drilling down into one of these examples, we know that in a merger or acquisition one company will need to merge operations, financial functions, business units, and other aspects of the enterprise with the newly acquired entity. This requires understanding of all levels of overlap and redundancy to develop a new operational plan which requires common definitions of processes, capabilities, rules, business units, customer types, etc. The role of business architecture in this type of scenario is to enable management, architects, and analysts to have a common view from a cross-functional and cross-disciplinary perspective. This “what if” scenario modeling puts business architecture at the center of the organization, and most importantly enables the company to have a common view of measurement and success.
Business architecture is a journey, not a destination – and the output of your work will constantly evolve too. Organizations like The Business Architecture Guild are working to make business architecture easier by establishing a network for business architecture to come together and creating industry standard reference models. Software is also creating platforms for business architecture by establishing capability maps in a dynamic environment that allows current state and dynamic “what-if” scenario mapping to test new strategies and outputs.
As Benjamin Franklin once said, “Without continual growth and progress, such words as improvement, achievement, and success have no meaning.” Utilize these three strategies to steer your business architecture efforts and you will also see improvement, achievement and success.
Want to hear more strategies to boost your Business Architecture Success?
Listen to our live panel discussion titled, "Business Architecture & Strategy Execution: Managing Risk, Scaling the Practice." MEGA Customer Success Manager and Enterprise Architect, Gordon Cooper led a robust conversation with Business Architecture veterans William Ulrich , President of TSG, Inc. and The Business Architecture Guild, Diane LeBeau , Chair of The Business Architecture Guild’s Executive Advisory Council, and Josephine Gilmore , Manager of the Business Agility Office at FedEx Services. They discussed strategies and real-world examples of how Business Architecture can help organizations manage risk and scale across the organization. Click here to listen.
... View more