<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Brian Mackey on Medium]]></title>
        <description><![CDATA[Stories by Brian Mackey on Medium]]></description>
        <link>https://medium.com/@brianwmackey?source=rss-e2a1365f0cc1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kFLrlfIKnI6pZFpprK0DOQ.jpeg</url>
            <title>Stories by Brian Mackey on Medium</title>
            <link>https://medium.com/@brianwmackey?source=rss-e2a1365f0cc1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 04:05:55 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@brianwmackey/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Random Acts of Agile]]></title>
            <link>https://brianwmackey.medium.com/random-acts-of-agile-2ec78dc45e26?source=rss-e2a1365f0cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ec78dc45e26</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scaled-agile-framework]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[enterprise]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Brian Mackey]]></dc:creator>
            <pubDate>Mon, 07 Dec 2020 16:06:10 GMT</pubDate>
            <atom:updated>2020-12-07T16:06:10.903Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hlka2FuTC3NgSgSAaTSIWw.jpeg" /><figcaption>How to manage the interdependencies of multiple squads</figcaption></figure><p><strong>Moving Agile Up to Enterprise Scale</strong></p><p>One of the biggest challenges for an IT leader in a company of any size is managing the interdependencies of multiple agile squads that are required to deliver a component of an End-to-End business capability.</p><p>Gone are the days where we marveled at a small squad of 6 people who used Agile methods to deploy a website that contained only static web content or at best had read-only syndication from multiple data sources but collected no data from visitors, processed no transactions and was integrated with no systems of record across the company’s enterprise architecture. Today we would look at such a project much the way we would look upon a child doing a “cannon ball” off the side of the pool while we are being asked to do a triple back flip with a twist off the high dive with a 50-pound pack strapped to our backs.</p><p>In today’s real world, most business capabilities require the careful coordination of multiple squads who must deliver items off their backlogs in order to fully enable the needed business capability. Take for example the simple concept of allowing customers more granularity in their communication preferences. All of the registration systems (e.g. Cookie Preferences, Communication Preference Center) must be enhanced to collect the information, the integration layer (e.g. API’s, ESB’s, ETL jobs) must be able to process and communicate the new information to the systems of record (e.g. Master Data Management, CDP, DMP) and then all of the systems of engagement (e.g. AdTech, MarTech, CRM, Customer Service) must now honor the customer’s new and more granular permissions. This simple business concept easily just broke down into work for at least 10 squads.</p><p><strong>Like Many Things In Life, It All Comes Down To Effective Communication</strong></p><p>There are many ways to ensure all of the squads are working towards a common goal but they all require additional planning and most of all good communication. Whether you choose to employ SAFe, Spotify or simply a Scrum of Scrums approach, the goal is the same and that is to ensure all the squads are deploying in a coordinated fashion and you avoid the dreaded “Random Acts of Agile”.</p><p>These Random Acts of Agile can be fairly benign where the end users are surprised by new features they weren’t expecting nor were they trained/enabled to use. This can lead to what I call “Enhancement Fatigue” where the end user communities become overwhelmed by the constant change in their user experience and they actually ask the engineering team to slow down or at least batch up the changes for formal releases that are accompanied by training and enablement.</p><p>However, these Random Acts of Agile can also be profoundly serious where they cause breakage in the end-to-end architecture because some of the squads had not delivered needed capabilities to handle the changes in up-stream or down-stream systems. The good news is that there are ways to allow squads to deliver at their own pace but not enable the new code until everyone is ready.</p><p>At the end of the day it all comes down to effective communication across the engineering teams and the end-user community.</p><p><strong>Management Tactics</strong></p><p>A decision point up front depends on whether or not the squads are using a common code base or separate ones. Having multiple squads working on a common code base complicates things and requires that the coordination amongst the squads moves down to the developer level. It will be important that common Continuous Integration (CI) / Continuous Deployment (CD) tools are used and careful management is in place with the various branches in the code stream, whether that is managed in Git or another source code control system.</p><p>Feature flags are a very effective method of allowing the teams to deploy production ready code at their own pace without the code becoming active until all the pieces are in place. A quick google search can provide plenty of details on how they work.</p><p>Feature releases are also something to consider to avoid the “Enhancement Fatigue” I mentioned earlier. This approach allows time to create enablement materials for the end user community, creating training videos, or even more formal training sessions.</p><p><strong>Enterprise Architecture &amp; Release Trains</strong></p><p>While some agile purists will tell you that squads will establish self-forming guilds where cross squad architecture items can be discussed and coordinated, but I’m not a fan of this approach. I strongly believe that you need people with enterprise and/or integration architecture experience proactively involved to ensure that the components delivered by the various squads all come together to support a properly functioning solution.</p><p>In addition, you will need someone who manages the interdependencies across the squads to ensure all of the components are delivered as needed for a full release of functionality. SAFe calls these “Release Trains” which are managed by “Release Train Engineers”. However, there are other methodologies with similar concepts such as Spotify, LeSS or Nexus. The specific methodology is less important than the focus on the roles and the need for these things to be proactively managed versus assuming they will happen organically because Agile is magic.</p><p><strong>To Sum Up</strong></p><p>In today’s high-pressure IT leadership positions, one of the biggest challenges in a company of any size is managing the interdependencies of multiple agile squads that are required to deliver a part business capability. There are scaled Agile methodologies that can help but there must be strong support from the management team to focus on an End-To-End view of what needs to be delivered to fully enable a new business capability.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ec78dc45e26" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In God We Trust, Everyone Else Must Bring Data]]></title>
            <link>https://brianwmackey.medium.com/in-god-we-trust-everyone-else-must-bring-data-f83111f156ed?source=rss-e2a1365f0cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/f83111f156ed</guid>
            <category><![CDATA[prioritization]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[it-portfolio-management]]></category>
            <category><![CDATA[stakeholder-management]]></category>
            <category><![CDATA[information-technology]]></category>
            <dc:creator><![CDATA[Brian Mackey]]></dc:creator>
            <pubDate>Mon, 02 Nov 2020 13:06:08 GMT</pubDate>
            <atom:updated>2020-12-21T16:44:45.005Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*b1QqoyMb865C2GYQteqJ2w.jpeg" /><figcaption>Solve the Everyone’s Request is a Top Priority Dilemma</figcaption></figure><p><strong>Everyone Thinks Their Top Priority Should Be Your Top Priority</strong></p><p>One of the biggest challenges for IT leaders in a company of any size is balancing all the competing priorities from a matrix of stakeholders. The larger and more global the company, the more complex and multi-dimensional the matrix of stakeholders become. Add to this the pressure most companies are feeling to move to a fully digital engagement model as most of the world has been in some level of lockdown due to the global pandemic and the demands on a companies IT organization will likely be well above their capacity to deliver.</p><p>Trying to manage this onslaught of request from various business units, divisions and geographies can be completely overwhelming and there are no easy solutions. However, I have seen best practices that work, albeit with a lot of focus and most of all good communication.</p><p><strong>Don’t Try to Manage It Alone</strong></p><p>It’s very easy for people to try and sell you on their idea for new IT capabilities when they are speaking to you one on one. They can be deeply passionate and seem to have lots of facts about the benefits. Anyone who has been in an IT leadership position for very long has experienced these, often in the hallway or at the proverbial water cooler, conversations where your new BFF praises your leadership and extolls the wonderful things your organization has done and how valuable your team is.</p><p>However, those very same people will take a vastly different approach when asked to present their idea in front of a jury of their peers. As such, it’s critical that you set up a fully transparent process where all requests come through a stakeholder council where they will be assessed by others who also want capabilities from the same IT organization. To be successful there must be an agreed upon method and template for describing any new business capability and the expected benefits. Putting this organizational discipline in place will magically make many requests simply go away as the requesters naturally start to think from a full company perspective instead of a parochial perspective.</p><p><strong>Learn How to Say “No” or “Not Now”</strong></p><p>One of the must subtle ways to lose the trust of your stakeholders is to accept items onto your backlog that you know will never get delivered because they simply do not have a strong enough value proposition to rise to the top of the queue. When you accept something onto your backlog there is a tacit agreement that it will be developed and delivered at some point in the future.</p><p>Using the stakeholder review process, it will become much easier as everyone is looking at the same list of items and the associated business value. It will be very clear what the roadmap looks like based on the cost/benefit analysis that will be transparently visible to everyone. While no one likes to hear “No” as an answer to their request; most people are mature enough to accept the answer and get on with business especially when they can see all the other requests that are in queue.</p><p><strong>Measure, Measure, Measure!</strong></p><p>Another good way to ensure that your stakeholders take the process very seriously is to ensure that you measure and report on the success, or the lack there of, for newly deployed capabilities. This should be a regular part of your stakeholder meetings. You can use a scorecard method to report on the outcome of previous approved requests. Doing that will inspire a healthy sense of competition amongst the teams as they try to deliver the most business benefits.</p><p>It’s also important that this scorecard is visible to the executives in the management chain above your stakeholder team. Your stakeholder team should be senior enough to be able to speak on behalf of their organization but also close enough to the front lines that they truly understand how the IT system is actually used. Maintaining constant communication with the executives will ensure your stakeholders active participation in the process.</p><p><strong>To Sum Up</strong></p><p>In today’s high-pressure IT leadership positions, having a fully transparent prioritization process is critical in earning and maintaining the trust of your stakeholders. Bringing the stakeholders into the process will also help ensure that the priorities that are agreed upon will be the ones that are in the best interest of the entire company vs an individual business unit or geography.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f83111f156ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Listen to What I Mean, Not What I Say]]></title>
            <link>https://brianwmackey.medium.com/listen-to-what-i-mean-not-what-i-say-582b8dc0be7c?source=rss-e2a1365f0cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/582b8dc0be7c</guid>
            <category><![CDATA[client-relationship]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[project-management]]></category>
            <dc:creator><![CDATA[Brian Mackey]]></dc:creator>
            <pubDate>Wed, 19 Aug 2020 14:18:20 GMT</pubDate>
            <atom:updated>2020-08-19T14:18:20.724Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C12a9Tr_I1-v1h74s4KL2Q.jpeg" /><figcaption>The art of making someone feel they have truly been heard</figcaption></figure><p><strong>How My Mother’s Words Guide Me Even Today</strong></p><p>The title of this blog is something my Mother would say to me when I had followed her instructions to the letter and yet didn’t do what she really wanted because she had misspoken in the heat of the moment. I think all of us can imagine the scene. A busy mom juggling many tasks and parenting multiple kids says to one of them “Go do task X” when she really meant “Task Y”. The child returns after completing “Task X” and she tells them that’s not what I wanted, but the child says that’s exactly what you asked for. To which the exasperated mother exclaims “Listen to What I Mean, Not what I Say”.</p><p>For those of you are having a chuckle over this as you think of your own parents or yourself, here’s the thing you should know. That lesson my Mother taught me has been carried with me throughout my career and has served me very well in working with my clients.</p><p><strong>You Didn’t Ask for This But I Knew You Needed It</strong></p><p>Creating an accurate Statement of Work (SOW) is one of the most challenging and important parts of any client engagement. If done properly it sets the expectations of everyone involved on what will be delivered, by who and how much it will cost. However, it’s still very easy to get into the classic situation where you deliver a complex, tripled decker swing that won’t work when the client really just wanted a simple tire swing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/612/1*wuXsVwhKekXjPN2KpO4MdA.jpeg" /><figcaption>Image Source — <a href="https://i2.wp.com/themoderndeveloper.com/wp-content/uploads/2013/05/UL_Cartoon.jpg">https://i2.wp.com/themoderndeveloper.com/wp-content/uploads/2013/05/UL_Cartoon.jpg</a></figcaption></figure><p>To avoid this, it’s really important to listen to what the client is trying to accomplish vs their exact request. I remember a situation where a client asked for an integration between their MarTech platform and their CRM. The exact request was “What would it take to build an interface” between the two systems. That’s a pretty straight forward request and the means of passing leads from a MarTech solutions to a CRM are not anything new. However, I knew they also needed a way to prioritize the volume of leads in order for them to be effectively managed, so I built a lead scoring solution into the estimate.</p><p>When I met with the client to review the SOW, I said to her “You didn’t ask for this but I knew you needed it, so I built it into the sizing”. She was grateful because she absolutely needed that as part of the solution, and I earned a lot of trust because I had listened to what she meant and not just what she said.</p><p><strong>The System Was Down All Day</strong></p><p>Many times, I have been in the position of mediating between end user communities and IT support teams as they have the “The System Was Down” debate. This too is an opportunity to listen to what the client means vs what they have said.</p><p>The IT Support team will typically react defensively and point out that the system was up and running and had processed thousands of transactions on the day in question without taking the time to listen to what the end user is trying to say. Typically, what the person is trying to express is that there was some kind of system issue that prevented them from completing the task they needed to accomplish that day. So, from their perspective the system was “Down”.</p><p>However, if the IT folks focus on what is said they miss an opportunity to truly hear their client. The best way I have seen to break this logjam of two different worlds is simply to ask the person “What were you trying to accomplish?” That opens the door for understanding at a much deeper level. It not only gives you the ability to help solve your client’s immediate problem but also provides invaluable information about how your product is being used and likely ideas on how to improve its overall usability. But again, you must take the time to listen for what the person means vs what they have said.</p><p><strong>To Sum Up</strong></p><p>Some of my best business skills were learned at a young age and good listening skills are at the top of the list. Learning to really listen to what you client means can change your relationship from one of an order taker to a trusted partner because your client will know that they have truly been heard.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=582b8dc0be7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data is the Antidote for Emotion]]></title>
            <link>https://brianwmackey.medium.com/data-is-the-antidote-for-emotion-74e1bd4ad03e?source=rss-e2a1365f0cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/74e1bd4ad03e</guid>
            <category><![CDATA[data]]></category>
            <category><![CDATA[martech]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[digital-marketing]]></category>
            <category><![CDATA[information-architecture]]></category>
            <dc:creator><![CDATA[Brian Mackey]]></dc:creator>
            <pubDate>Thu, 23 Jul 2020 15:12:20 GMT</pubDate>
            <atom:updated>2020-07-23T15:12:20.498Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ny5xfCFjqf3oco4RX55hkA.jpeg" /><figcaption>Good data can dissolve high pressure situations</figcaption></figure><p><strong>Our High-Pressure World</strong></p><p>In today’s “always-on”, “what have you done for me lately”, “do more with less” world that we all live in, constant stress is a given. We all feel the pressure to continuously deliver outstanding results so we don’t end up on the next layoff list, and that was the case even before the new world of COVID lockdowns which put roughly 35 million people in the US unemployment lines.</p><p>With everyone feeling that level of pressure, our interactions can become highly emotional experiences despite everyone’s best efforts to remain calm. None of us are fully immune. The good news is that emotional conversations can be converted into fact-based conversations with a small investment in good data collection.</p><p><strong>The System Is Down Again!</strong></p><p>For those of us who develop applications or those who use them, this is one of the least favorite conversations. Product Owner says, “I’m getting complaints from all over that the system is down”. Application manager says, “I don’t have any support tickets”. The conversation gets worse from there and is likely full of emotion on both sides.</p><p>With modern instrumented monitoring of applications and full transparency this can be a completely different conversation or better yet not even a conversation at all. Modern monitoring tools are now capable of instrumenting applications with “use case” monitoring that simulate actual user activity. In addition, they can run the tests from multiple geographies. This gives the application support team advanced notice of issues even though the low-level IT monitors (e.g. CPU/Memory/IO utilization, Transaction Volumes, etc.) are still all green.</p><p>Next, by putting this information in a dashboard that is visible to all end-users, you are then enabled to have a fact-based conversation like this. Application manager calls Product Owner and says “We have detected an issue with Use Case X for users based in China. Everything else is working properly. We have opened a ticket and are investigating it now”. Clearly, that is the conversation that anyone would rather have.</p><p><strong>We Must Squeeze More Into The Next Sprint!</strong></p><p>I can still remember the day I became a fan of the Agile methodology; it came when I heard a Product Owner and Development Manager talking about the approach. The Development Manager said, “Our squad has a velocity of 250 story points, we need 50 points to address technical debt so the Product Manager’s budget for the next sprint is 200 story points.” What a healthy way to manage that relationship!</p><p>The only way to enjoy that kind of fact-based conversation versus an emotional conversation is having the data. Therefore, the impetus is on the agile squad to be very diligent in assigning story points to the stories on their backlog and then tracking the squad’s velocity. The absence of that diligence leads to emotional conversations where the amount of work that gets crammed into your next sprint devolves into a battle of wills.</p><p>Having a well-groomed backlog with good story point estimates and well tracked velocity that is fully transparent to the entire squad and product owner easily focuses the conversation on the facts.</p><p><strong>Our Conversion Rates Are Terrible!</strong></p><p>Any good Digital Transformation leader will be extremely focused on the conversion rates at various points across their company’s digital funnel. This is a good start because the conversation is starting with data. However, from there it can easily descend into speculation on the root causes based on gut feel and intuition.</p><p>Let’s use the example of live chat. We have all seen the live chat icon on a website or seen a pop-up invitation to join a chat. Sometimes they are welcome and sometimes that are nuisance. How do you know which approach works best? The good news is that there are tools that can easily run A/B, or even better, multi-variant tests on your website. These tools will randomly offer different experiences to your customers, track the results, and then tell you when they have collected enough data to make a statistically significant recommendation.</p><p>Once you have that information, you can then have a fact-based conversation on the changes you should make to improve your conversion rates.</p><p><strong>We Can’t Survive Without A Guaranteed Paycheck!</strong></p><p>Many have considered leaving the security of a regular paycheck in favor of running their own business. One of the key fears of course is wondering how long you could survive on your savings while you try to get your new business up and running. For many that conversation is based purely on gut feel, which would leave anyone with a lot of anxiety.</p><p>Luckily, there are a lot of easy-to-use tools available today that can quickly import your spending transactions from your bank, credit card companies, and others. These tools have also become particularly good at automatically categorizing your spending, so you can see exactly where your money has been going with very little effort on your part.</p><p>Spending as little as 15 minutes a week importing your expenses can provide you with immensely valuable data as you consider the budget you need to live on and provide you the facts you need as you consider venturing out on your own.</p><p><strong>To Sum Up</strong></p><p>It’s hard to put a price on collecting good data and it’s easy to be pressured into putting it off, but after a few difficult emotional-driven conversations, you will be wishing you had invested the time for collecting good data so you could have a fact-based conversations instead.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=74e1bd4ad03e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Do Not Fall for the Hype — API’s Are Not Magic!]]></title>
            <link>https://brianwmackey.medium.com/do-not-fall-for-the-hype-apis-are-not-magic-bdc4715ef262?source=rss-e2a1365f0cc1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bdc4715ef262</guid>
            <category><![CDATA[information-architecture]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[integration]]></category>
            <category><![CDATA[marketing-automation]]></category>
            <category><![CDATA[martech]]></category>
            <dc:creator><![CDATA[Brian Mackey]]></dc:creator>
            <pubDate>Thu, 09 Jul 2020 15:03:28 GMT</pubDate>
            <atom:updated>2020-07-09T15:03:28.508Z</atom:updated>
            <content:encoded><![CDATA[<h3>Do Not Fall for the Hype — API’s Are Not Magic!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tOYA028WHC_vipOK" /><figcaption>Photo by <a href="https://unsplash.com/@officestock?utm_source=medium&amp;utm_medium=referral">Sebastian Herrmann</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p><strong>The SaaS Revolution</strong></p><p>The wide availability of pay-as-you-grow SaaS applications have revolutionized the way IT is delivered and has lowered the barriers to entry for entrepreneurs all over the world, and that is a great thing! Gone are the days of setting up your own data center, purchasing expensive servers to host your company’s applications and then hiring a large IT Infrastructure team to support it.</p><p>In today’s word you can provision a SaaS application for your company in minutes and at extremely low or no cost to start with. As your company grows the solution grows with you. All of this is incredibly good news for businesses of all sizes, but the age-old IT dilemma remains true … how do we make all this stuff work together?</p><p><strong>The Integration Dilemma</strong></p><p>The marketing hype will tell you that you need not worry about integration because these new breed of applications come with out-of-the-box API-based connectors for integration and we all know API’s are magic … right?</p><p>Well, the answer isn’t that simple. Yes, API’s absolutely make connecting your portfolio of SaaS applications easier. However, this is like creating a new way of quickly and easily connecting the plumbing in your new building. It is a great improvement because it reduces the cost of the plumbing but here is the real problem. If your water is dirty, you have just made it very fast and easy to disseminate your dirty water to every part of your building. That is when “SaaS Happens”.</p><p>Better methods of IT plumbing do not provide you with better data, good Information Architecture does.</p><p><strong>Cloud-Based ESBs Help but Don’t Solve the Fundamental Issue</strong></p><p>One of the great things about today’s economy is how fast new solutions can be brought to market when there is a need. Many companies have seen the need to orchestrate the integration of a heterogeneous, best-of-breed portfolio of SaaS applications. These new cloud-based Enterprise Service Bus (ESB) solutions take API’s to the next level and when implemented properly do get companies closer to the “Plug-N-Play” panacea that everyone dreams of.</p><p>But again, this is just improvements on the plumbing. There is value in having that kind of capability, but it too does not solve the fundamental dilemma of disseminating bad data, good Information Architecture does.</p><p><strong>Information Architecture is Still Critical</strong></p><p>I remember a large presentation I was part of where a new Marketing Dashboard was being demonstrated. It was a thing of beauty and the various marketing leaders across the company were drooling in anticipation of putting it to use. Then they were asked to focus on the roll-up of the data by product offering and it was clearly not good at all. The root cause was easy to identify, bad information architecture. There was no standard in place for the product taxonomy that was used consistently across the systems of engagement. So, even though the IT plumbing had been put in place to pull the data together and a shiny new dashboard had been built, it only served to make it fast and easy for everyone to see how bad the data was.</p><p>No matter how much the technology improves, the fundamental need for good Information Architecture will always remain. The challenge is often that talking about data standards, common taxonomies and the enterprise governance to enforce them is not an exciting conversation. However, in the absence of those things your “exciting” conversations will be explaining why the data looks wrong and is not trustworthy.</p><p>The good news is that developing a good Information Architecture is not expensive. Further, enforcing it at the start of technology deployment is not expensive and can actually reduce costs if there are reusable assets for managing and consuming approved taxonomies. Unfortunately, cleaning up the mess after a large technology deployment done without good Information Architecture can be very expensive.</p><p><strong>Need Strong Data Ops at the Edge</strong></p><p>Finally, even after getting good integration plumbing in place and strong information architecture there is still room to improve the quality of your data by adding sophisticated Data Operations monitoring. The items we have discussed so far will ensure that your data is properly connected and using common taxonomies so it can be aggregated, but what happens when something goes awry? No one likes getting the call “I haven’t seen any new leads for product X in the last 3 weeks”.</p><p>It is also important that you put intelligent monitoring in place that can detect large fluctuations in transaction volumes flowing across your integration architecture. Think of it like fraud alerts you get from your credit card company. They alert you when they see a transaction that deviates from your normal purchasing pattern. Similarly, if you normally see 50 leads per day for product X and it goes to zero for several days, it is probably worth someone investigating.</p><p><strong>To Sum Up</strong></p><p>Yes, the IT world is a better place today with the ability to easily stand up pay-as-you-grow SaaS solutions that integrate much easier with other applications, but these improvements only lower the cost of the IT “plumbing” and do not eliminate the need for strong Information Architecture.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bdc4715ef262" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>