Tuesday, 01 November 2011 10:04

The Bad Ass BA: “Business Architect”?

Written by
Rate this item
(22 votes)

FEATURENov1stWhat the heck is a Business Architect? 

I have had the title Business Architect for almost a year now — I’m loving it. With about thirty years’ working experience in software and the last ten years in the role of business analyst, the next step for me was business architecture, but if you asked me a year ago what that meant, I wouldn’t have been able to give you a succinct answer, or tell you the elements of the discipline. It was something about the connotations of the word “architecture” that attracted me. The notion of integrating all the functionality together, having hierarchies of taxonomies in your head, ooh, ooh! But thinking and doing take more than a little effort to link. Sometimes stubborn people like me need a kick in the rear from the universe to get moving. So while I didn’t like getting laid off last year, because as much as I was relieved to be out of there, my pride was hurt, it was time to go and it forced me to recalibrate myself professionally and make the leap.

The trouble was, there was so much conflicting information about the role of the Business Architect. There’s lots of conflicting opinions on the differences in focus between an Enterprise Architect, a Business Architect, an Information Architect and a Process Architect.

Being intuitive and somewhat reckless, when the interview question came up from the Enterprise Architects about what technologies I would recommend, I heard these words coming out of my mouth, “Gentlemen, you shouldn’t be hiring a business architect to advise you on technologies. I may have my opinions, but there are far better qualified people out there for that. I would be bringing you information about business needs and business processes, not on technologies or solutions.” This was a phone screening. There was dead silence on their end of the line. Darn it, Cecilie, you’ve stuck your foot in your mouth again, I thought to myself. Then, I hear, “Okay! Would you tell us about a situation in which…” Whew, they were still talking to me.

I knew I could do the tasks identified in the job description, but I knew I had to get ahead of the professional development curve if I was going to succeed in this role in the long term. After a few months on the job, there was an opportunity to take the equivalent of Business Architecture 101 at a conference, so I signed up for two 1-day seminars. One of the seminars was just okay. The second one was mind blowing — one of those experiences where every synapse in your brain is pulsating and your neural matter hurts for days afterwards because new neural pathways are forming, and old, deep patterns that have never been challenged before have been cauterized out. I walked around for a week after that seminar like a grinning fool.

I needed definitions and I got ‘em. After keeping these definitions in the back of my mind for the past six months, I’m ready to share — they are valid and I hope you find them useful for your career development and for your endeavors in the Enterprise Analysis knowledge area of the Business Analysis Body of Knowledge.

What is Business Architecture?

First, a business architecture is not a business function/process model. Most business process models show an inventory of processes, but not an integrated model of the information used by those processes. Most business function/process models do not show the customer/consumer/end user or how that customer perceives the touch-points between the business processes and functions.

Business Architecture occurs when you integrate two or three or more different core cross-functional business processes in an engineering type of model, and as a result, make things more clean and efficient. This model is the beginning of an enterprise business architecture. The definition I use is a model of an enterprise (single company or industry) that shows the integration points of all the information that enables the enterprise to function. The model shows information sources, destinations and transformations.

Furthermore, for a single company, a business architecture is just one element of an integrated enterprise architecture. The integrated enterprise architecture includes business, technology, security and organizational architectural components to create a complete model. In addition to all the modeling techniques I have used as a business analyst, I have added capabilities, value streams and value chains to my bag of modeling techniques.

No discipline is without its controversies and the usefulness of basing an architecture on capabilities is one of those controversies. Here’s a definition of capability: the ability of an organization to use its assets to accomplish an activity that delivers business value or competitive value. I have memorized that phrase and can spout in out in my sleep. I can’t build a model of a capability that would stand up to a spring rain. Still, I see long threads on the business architecture discussion sites focused on how best to model “our unique ability to do <pick your favorite activity>”. When the focus shifts solely to a linear process without a view of the integration points, I get worried.

A value stream is an end-to-end collection of activities that creates a result for a customer. The value stream has a clear goal: to satisfy or to delight the customer. “Delighting the customer” is a well-known phrase that comes to us from the Six Sigma and Lean Manufacturing disciplines.  

Some examples of strategic visioning value streams are “insight to strategy,” “vision to eBusiness enterprise,” “concept to development,” “initiative to results,” and “relationship to partnership.” At Railinc, because the business architecture function is new, one of the first things my team had to do was define an “initiative to results” value stream and integrate it with the product management team activities.

You may be familiar with some customer-centric value streams such as “prospect to customer,” “lead to cash,” manufacturing to distribution,” and “request to service.”  Business analysts are also typically deeply involved with business-enabling value streams such as, “forecast to plan,” “requisition to payables,” “resource availability to consumption,” “acquisition to obsolescence,” and “financial close to reporting.” People caring is another category of value streams, “recruitment to retirement” (less politically correctly known as “hire to fire”) and “awareness to prevention.”

I’ll go into value chains in a future article, but for now I just want to say that value chains are part of what a business architect builds. A value chain is a sequence of activities followed by a company in a specific industry. The chain of activities gives the product more added value than the sum of the independent activity's value. As a simple example, take a master chocolatier as a profession. Cocoa mass, sugar, cocoa butter and dark chocolate nibs are low-cost ingredients by themselves. In the hands of a master chocolatier, the result can earn you forgiveness for leaving dirty socks on the living room floor, show appreciation to that analyst who went the extra mile for your study, or, eaten in private, could get you lucky on a date. The making of a chocolate confection may have a low cost, but the activity adds much of the value to the end product since the ingredients are significantly less valuable than a box of Recchiuti Confections. 

So, what do you do with a value chain? Once you have the value chain, in order to understand the behavior of costs for the product you can disaggregate a company (don’t be distracted by the divisions) into its strategically relevant activities. And you can examine the existing and potential sources of differentiation between your company and your competitors. Does your competitor have the ability to deliver a service in the same end-to-end capacity as your company can? Does that make you more interesting to potential customers? Understanding the value chains enables a company to gain a competitive advantage by performing these strategic activities more cheaply or better than its competitors.

What is the goal of Business Architecture?

In my opinion, the goal of a business architecture is to enable a company to focus its services on its customers. If you don’t know how the information in your company is integrated to enable delivery of services and customer satisfaction as well as being able to bill and collect for those services, then your company is in trouble. 

Case in point, what happens when you have multiple customer master databases? It is easy for this to happen. In my previous company, we grew by acquisition. With each new acquisition came at least three customer master files, one from the sales group, one from marketing and one from customer service. In my current company, we are in the process of integrating the customer master files associated with siloed products. One of the driving issues is data quality; when you have multiple sources of the same data, but no process for “single source of truth,” it can be impossible to know what is the most current data set for a customer. To achieve the goal of a single customer master file a company has to have an integrated model of customer touch-points. I don’t know about you, but I hate getting “exceptional offer for new customer” announcements from a service provider that I already have a contract with, especially when I see what good deal I would get if I weren’t already a customer. Makes me wonder if a competitor might match that new customer offer.

Rethinking “The Customer is #1” idea

A short tangent, indulge me. I’ve never liked the idea of the Customer being #1. In my mind, the employees should be #1 because if the employees are treated well they will perform well and treat the customer well and make the customer feel like they are #1.

In a previous company that I’ve worked for, if a customer became difficult to work with, one question that was always on the table was, are they worth doing business with? We could quantify that answer in terms of revenue versus lost productivity dealing with them and low employee job satisfaction. There’s a ceramic urn on top of the refrigerator in the employee break room at that company labeled “ashes of former customers.” I can’t tell you how much employee loyalty that urn evokes; I can tell you that in that urn are the names of companies we stopped doing business with because management decided it was bad business.

My employer, Railinc, is a subsidiary company of the American Association of Railroads. Having never worked for a subsidiary company before, I was surprised when I realized that one piece of advice that has been in my toolkit is no longer applicable — Railinc cannot fire any of its customers. We can’t single out a particular railroad and say, “We won’t do business with you.” A new twist in the life of an information worker.

Does making the employee “#1” conflict with the goal of a customer-centric business architecture? Not at all. It just means that a company needs to examine its business goals and determine the different aspects of “the customer,” i.e., revenue source and cost-center if it wants to broaden its definition of “customer.” Customers aren’t just revenue sources; they are also sources for cost, as in customer-retention. Employee-retention is also a quantifiable asset. Revamping the definition of customer is one example of how thinking at the enterprise level changes the scope of a business analyst to business architect.

What does a Business Architect do?

Like the job description for a business analyst, the answer to that question seems to be dependent on the hiring manager. There’s lots of confusion between the role of the enterprise IT architect and the business architect. I can only tell you what I am and am not doing.

Currently my focus is on core elements of the industry, specifically railcar health and railcar utilization. My days are spent as follows:

  • Formulating frameworks and building models — by the bucket load
  • Writing concept documents
  • Critiquing project proposals
  • Preparing for and conducting knowledge elicitation meetings
  • Asking a lot of questions
  • Collaborating, facilitating, more collaborating
  • Identifying “services” in product offering visions
  • Tending an organic (constantly changing) ten-year roadmap

I do not research or recommend technologies. That’s doesn’t mean I can be ignorant of past or current technologies. In fact, being older and having been around when some of the legacy systems were built and understanding how difficult it is to migrate off those platforms has been beneficial. I leave the “how” of the solution to the enterprise architects. They come to the business architecture team for the “what do they need to do and why do they need to do it.”

In my current position, my scope of work isn’t a single company. Railinc provides information services to the railroad industry. The business architecture model that my team is building focuses not on a single enterprise but on the entire railroad industry.

What I don’t do is spend any time with UML, write formal requirements and work directly with the product developers. That experience prepared me for how I spend time now — working with people at the railroads, with Railinc business analysts, product managers, program managers, Railinc enterprise and data architects, and external industry subject-matter experts. 

I help articulate our products, current and future, in terms of services and value streams. In particular, I analyze railcar health and utilization information and integration points in terms of relationships to all external entities, other enterprise value streams and the events that trigger instantiation. I look at railcar health and utilization information from the perspective of what my company must produce to satisfy its industry partners, compete in a market and deal with its information suppliers.


If you can’t help but perceive the world around you in terms of business information needs and process and connections; if you can hold multiple points of view simultaneously; if the meta-modeling is part of your consciousness and you’ve had a blast being a business analyst and are looking for something more, then I strongly encourage you to start aiming your career at business architecture.

Recommended Reading

Google these:

  • The Outside-In Approach to Customer Service, Sarah Jane Gilbert
  • “You Can’t Cost-Justify Architecture,” John Zachman
  • “Converging Business Architecture Approaches,” article on BPMInstitute.org

This book was published this year: Enterprise Business Architecture, by Ralph Whittle , Conrad B. Myrick 

Don't forget to leave your comments below.

Cecilie Hoffman's professional passion is to educate technical and business teams about the roles of the business analyst and business architect, and to empower business analysts with tools, methods, strategies and confidence. A motorcycle enthusiast, she’s riding out the downturn in the economy by living a bicoastal life, living in California and working as a business architect at Railinc in North Carolina. Her friends have disqualified her from the “how far do you commute to work” contest on the grounds that she’s nuts.

Read 68154 times


+2 # Jon 2011-11-01 05:35
Absolutely terrific and informative article!! Also very timely...in the past 5 years the role of "architect" has been popping up much more frequently. In my line of business there also seems to be much confusion about the roles of Application Architects (IT), Business Architects, and Enterprise Architects. I like your detailed description and examples you give of the business architecture role. As a 20 year IT and business analyst veteran, business architecture is a role I want to work into. Your article resonated with me. Thanks for sharing your experience, and I’ll check out your recommended reading too!
Reply | Reply with quote | Quote
0 # Pat Folkerts 2011-11-01 05:35
Hi Cecilie. Great guidance here. Thanks so much. Would you share the source of conference #2 mentioned in your article (. . . Business Architecture 101 at a conference, so I signed up for two 1-day seminars. One of the seminars was just okay. The second one was mind blowing . . . .)?
Reply | Reply with quote | Quote
0 # Nirmal 2011-11-01 05:55
Identical to what i perceived to be a true Business Architect....Ex plained in very simple words and hits the nail on the head.....
Reply | Reply with quote | Quote
+2 # Karen 2011-11-01 06:59
Engaging well-written article! One question: If you build models by the "bucket load" but don't spend any time in UML - specifically, what types of models are you building?
Reply | Reply with quote | Quote
0 # Nick 2011-11-01 10:10
An important and well-written article, thanks.
Reply | Reply with quote | Quote
0 # Cecilie Hoffman 2011-11-01 11:16
Pat: Take a look at BPMIinstitute.o rg. They have at least two tracks - Business Process and Business Architecture. The mind-bending class that I took that was "Building a Business Architecture using Value Chains & Value Streams" presented by Ralph Whittle, he is the co-author of Enterprise Business Architecture: The Formal Link between Strategy and Results. BPMInstitute offers four conferences a year. I took Mr. Whittle's class in San Francisco. Not all classes are offered at each conference - a word to the wise. I'll go out on a limb and recommend William Ulrich's class, "Business Architecture / IT Architecture Alignment: Cross-Disciplin ary Alignment Strategies for Business & IT" because people I trust say it was a good class and he is a good speaker.
Reply | Reply with quote | Quote
0 # Cecilie Hoffman 2011-11-01 11:28
Karen: Let's look in the buckets and see what's there. I can see some business context models, some business process flow charts, several SIPOC (supplier input process output customer/consum er) charts, bunches of concept diagrams that show an abstract idea, like "railcar repair business cycle" which then decompose down to specific activities like the process of a mechanic closing out a repair work order and that information getting propagated into the systems that close out the health alerts on that railcar that trigger the repair workorder. Hmm, here plastered against the side of the bucket are a couple of RACI charts as well as I try to sort out who is doing what. At the very bottom are a couple of system interaction diagrams as well - I had to figure out where the information needed to answer a specific business question was coming. Does that help you?
Reply | Reply with quote | Quote
0 # Salman Saleem 2011-11-01 15:47
A very thought-provoki ng article. Thank you for sharing your experiences Cecilie!
Reply | Reply with quote | Quote
0 # Ken Livingston 2011-11-01 15:53
Very interesting, Cecilie, and very timely. I'd only bumped into the role of Business/Enterp rise/Whatever Architect a few months ago, and it seems that the architects here are predominantly systems architects in practice, regardless of their actual title - they're very solutions-orien ted. In any case Business Architect is certainly a role where I thought "I could do that!", can see a need for one where I am now, and have started asking questions... I see the role of Business Architect as an ideal career progression for a lot of BA's (well, me at least) because it offers a lot more strategic level work, without the burden of having people working for you. As you say, it draws on a lot of the skills that we use day to day. I like the idea of indentifying (or developing) the capabilities, value streams, and value chains. "The customer is #1" is a bit of an outdated concept now - the focus has shifted to looking after stakeholders, which includes employees, customers, suppliers, shareholders, and so on. It doesn't get away from the fact that any organisation still has to put themselves in the customer's shoes and actually do some thinking about what customers want and how they interact with the organisation. Congratulatio ns on moving from being a BA to being a, well, er, BA, and thanks for giving us a summary of what a Business Architect does.
Reply | Reply with quote | Quote
+1 # Cecilie Hoffman 2011-11-03 08:48
Ken: glad to hear you say virtually speaking that "the Customer is #1" is considered outdated. So is the rotary telephone but those of us over 30 recognize that icon - my point being that the idea persists and needs persistent re-examination to show the fallacy of the perspective. As for going from BA to BA, it is rather zen, don't you think? I'm so relieved I didn't need to change my moniker.
Reply | Reply with quote | Quote
+1 # Cecilie Hoffman 2011-11-04 01:50
Andreas: the practice of business architecture is new at Railinc and we are a small company. Have you already guessed the tool for model rendering? Yup, Viso. As for where my models are stored, weIl, for the purposes of drill-down, right now I simply give my models to people who I know would be interested - they use them for their own purposes and that sharing has been key to selling the idea that busines archticture is a valuable activity. Railinc has a wiki and I make my stuff available on my personal Sharepoint site. Establishing a library of re-usable models is definitely part of my vision for my group, but we need to climb that mountain one step at a time. If you were looking for a recommendation for one of the enterprise-leve l ERP database integrated big honkin' tools that will also run simulations, sorry, not in my toolkit right now... like drooling over the BMW i3 electric car, so close and yet not quite within reach.
Reply | Reply with quote | Quote
0 # Sujatha 2011-11-09 15:15
Hi Cecilie, This article is simply awesome! I get to read this stuff at the right time. I have been shortlisted for a Business Architect profile in a very well known and reputed organization and was wondering how they mapped my profile for a Business Architect. Currently I'm a business analyst and have been wondering what will take me to the next level. And after reading this write up I realize that I'm aleardy doing some of the business architect's tasks! Thanks for sharing this - it has been really useful and enriching. Tha nks, Sujatha
Reply | Reply with quote | Quote
0 # Cecilie Hoffman 2011-11-09 21:32
Sujatha, you have made my day. All the best to you in your new role!
Reply | Reply with quote | Quote
0 # Neal McWhorter 2011-11-17 15:37
Nice article! Just thought that I would point out that the Business Architecture Guild (www.businessarchitectureguild.org) in combination with the Business Architecture SIG at the OMG (basig.omg.org) are in the process of creating both a Handbook defining the core knowledge areas for Business architecture and a standard framework, respectively. This combined effort should help bring to an end much of the confusion around business architecture. Neal McWhorter Co-Ch air OMG Business Architecture SIG Founding Member, Business Architecture Guild
Reply | Reply with quote | Quote
0 # ellen gottesdiener 2011-11-29 06:19
fabulous, informative, compelling and fun to read. thanks Cecilie!

thank you for writing this article.
~ ellen
Reply | Reply with quote | Quote
0 # Traci Fogle 2011-11-30 01:03
This was a great article and cleared up a few things for me. Thank you!
Reply | Reply with quote | Quote
0 # andre Pharand 2011-12-09 04:46
My God! Finally, someone saw the ligth! Congratulations !
Reply | Reply with quote | Quote
0 # Gert vd Westhuizen 2012-11-12 03:03

Agree! Good article.

Business Architecture is the vital component for the engineering of the enterprise.

We have tried to come up with an Engineering framework for Business, Process and Technology Architecture and our efforts are available for comment and scrutiny here : http://www.discon.co.za/Public/About/WWD.aspx

Gert vd Westhuizen
Reply | Reply with quote | Quote
0 # Dave Laurentino 2012-12-19 22:33
Thanks for the great article, currently I am a Unified Communications architect working at RIM. I have been enrolled in a Enterprise Architecture course at the University of Toronto.
Its been nothing but a eye opener, I do want to learn more and take a mentor role in a business/enterp rise architecture role some place in the future. Your article was very informative.

Dave Laurentino
Reply | Reply with quote | Quote
0 # Shiva 2012-12-26 10:06
Can anyone please provide the most common frameworks used for Business Architecture ?
Reply | Reply with quote | Quote
0 # Sanum 2013-01-06 16:21
Great article. Where is the BA function positioned in the organization. Where I am its is in IT and that brings a lot of challenges trying to decouple business architecture from business requirements and solution delivery. Teams are getting frustrated as we are seen as the entry point to solution requirements which obviously is not the case
Reply | Reply with quote | Quote
0 # Pete 2013-04-04 09:56
From a software architect to a business architect, it is latest kick in the teeth from my employer. This article is supposed to make me feel better. From what I read, BA is short for boobs on a bull.
Reply | Reply with quote | Quote
0 # Mukesh agrawal 2013-10-11 00:47
nice article , really helpful who is willing to be a Business architect
Reply | Reply with quote | Quote
0 # Osama 2013-11-29 12:24
I have read to much about BA but I did not get a clear picture what is BA and for what. this article put me on the right track and covered all sides that I was looking for.
Reply | Reply with quote | Quote
0 # Petro 2014-03-07 00:31
Dear Cecile

In your opinion what is the difference between a business analyst and a business architect, and who do these work together / support each other?
Reply | Reply with quote | Quote
0 # Seriously 2014-03-11 21:44
Thanks for the article. It is now clear as mud. I'm guessing that the job description also includes using too many words to say something that could be done in less.

Thanks. Fun Read. Not.
Reply | Reply with quote | Quote
0 # Nagesh 2014-06-27 06:47
Very thought stimulating article on the role of a Business Architect ... it is a wonderful point that Employee is #1 ... customer is the reason for your business and cannot be numbered because customer is the ultimate .... this was brought out very well... In some process oriented organizations, they have a Architecure framework which defines the activities as part of architecture lifecycle and multiple architects work on the activity depending on the type of deliverable... in this way the roles are not compartmentalized.
Best wishes
Reply | Reply with quote | Quote
0 # Pino 2015-05-25 04:55
To me it seems that BA is just a step up from BPM. It fails to address systemic conditions; value stream mapping is of little value without understanding system dynamics; understading dominant properties that determine system state. Value stream mapping is OK for theory limited value with respect to reality. Try and play the beer game with value stream mapping and realize all the limitations. BA have no tool-set to understand and manage adaptability; therefore doing the right things that are need considering system conditions. BA does not have tool set to undertand context; therefore the organizational mgt structure needed for ensuring viability. BPM, BA, BTM (exponent 2) yes exponent 2 are all intiative developed to address major shortcomings but always missing the point.
Reply | Reply with quote | Quote
0 # Dipti 2015-06-19 11:59
This article is very useful to me as a career BA transitioning to Business Architecture. Thanks for spelling it out in lamen's terms. Coincidentally, I used to work at Railinc in Chicago as a mainframe programmer, around the Y2K "crisis". Funny to hear that name again, and interested to hear that it has expanded and doing business architecture.
Reply | Reply with quote | Quote
0 # Tayo 2015-07-03 23:33
Hello Cecile. Just wondering if there is a training for B-Arch and would you recommend
any training
Reply | Reply with quote | Quote
0 # MJ Crabbe 2016-03-30 11:40
Thank you for the valuable information and perspective. Would you be willing to share any suggested courses or seminars or speakers that would add depth to these concepts. I read that you attended one with positive results...
Reply | Reply with quote | Quote
0 # Andrew Frazier 2016-04-13 10:21
Great article! I appreciate you sharing. In effect, I have find myself as an independent business architect for small and medium sized organizations. The information in this article will help me to communicate how I add value more effectively.
Reply | Reply with quote | Quote
0 # Rita DiMartino 2016-10-06 07:58
Ronnie, I am trying to set up a Business Archtecture practice as part of my consulting engagement - thought you might be interested - its both strategic and conceptual, something that matches your intellect. Tlak soon, rita
Reply | Reply with quote | Quote
0 # Jennifer Abbott 2017-03-08 11:08
Timeless. I just recently moved into the Biz Architect position and ready your words was like a page from my life. Very grounding to be in good company. Thank you for sharing on the interwebz so that I may find it in my journey.
Reply | Reply with quote | Quote

Add comment

Security code

© BA Times.com 2016

DBC canada 250