<?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 Matt Armstrong on Medium]]></title>
        <description><![CDATA[Stories by Matt Armstrong on Medium]]></description>
        <link>https://medium.com/@mattarmstrong_68463?source=rss-24502ab8fec4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*nLnwNkwIXWC6xem0.</url>
            <title>Stories by Matt Armstrong on Medium</title>
            <link>https://medium.com/@mattarmstrong_68463?source=rss-24502ab8fec4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 18:42:42 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mattarmstrong_68463/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[The 10 Things I Learned Leading FP&A Teams through Crises]]></title>
            <link>https://medium.com/@mattarmstrong_68463/the-10-things-i-learned-leading-fp-a-teams-through-crises-c6f05cb1742b?source=rss-24502ab8fec4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6f05cb1742b</guid>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[crisis-management]]></category>
            <dc:creator><![CDATA[Matt Armstrong]]></dc:creator>
            <pubDate>Sat, 21 Jan 2017 21:54:11 GMT</pubDate>
            <atom:updated>2017-01-21T21:54:11.695Z</atom:updated>
            <content:encoded><![CDATA[<p>Imagine you come into a new job thinking that it was going to be a challenge — then it turns out to be <strong>not just</strong> a challenge but instead it’s a <strong><em>massive crisis</em></strong> — systems are not up to date, processes are broken, most of the team has left, etc… I have confronted this opportunity twice in the last seven years working for large online ecommerce companies. In both cases, I needed to manage the crises and turn the FP&amp;A teams around … fast.</p><p>We were able to turn them around both times, but not without a lot of blood, sweat and tears. We all made some mistakes, but everyone involved learned a ton with a bit of fun thrown in (depends on who you ask though…). If you haven’t been through a crisis, you will find out a few things that you weren’t prepared for — and boy, did I need to figure a lot of these things out quickly!</p><p>Below are some of the key learnings from my experiences that I hope you can apply in your FP&amp;A environment if you happen be in a crisis yourself.</p><h3>1. I believed that a crisis was a massive opportunity — I didn’t want to let it go to waste!</h3><p>It is a rare situation when working at a large or established company that you have the mandate to make change and everyone in the organization clearly understands this.</p><p>Conversely, change is difficult to implement when the business is running smoothly — there is inertia to do the same thing over and over again. In most cases in a large organization, the processes are probably barely working and would cause too many problems to change them, and/or people hate change, and/or there is no political will to make change.</p><p>Being in a crisis allows you to make that change and do the right things in order to be successful — I had that opportunity and I seized it! However, getting others to see this as an opportunity also proved to be challenging — very few qualified people wanted to apply for roles that I posted. Those who took the chance realized the impact they could make and were the right people I wanted on my team.</p><h3>2. A significant amount of energy, optimism and confidence is necessary to manage a crisis</h3><p>In the most challenging crisis of the two, wherever I looked, there was this negative view of the FP&amp;A team: how they operated and partnered with others created mistrust and a fear of failure. The inertia of failure that existed had to be turned into an expectation of success — project the positivity and get the team to buy in. We had to believe we were going to get this transformation done and my team fed off of this positivity to deliver what was expected.</p><p>Having this positivity unfortunately had some drawbacks. We tended to underestimate time and resources necessary to complete tasks because we were so positive that we would succeed. So we were given a dose of reality for certain milestones, but that didn’t dampen our enthusiasm to reach our goals. In fact, this enthusiasm carried over to others in the organization who previously weren’t drivers of change and helped change the culture of the organization. So having this positivity was in reality a net benefit to solving the challenges.</p><h3>3. Fixing an FP&amp;A team in a crisis required changing processes, systems and people — all at the same time</h3><p>In both crises, I quickly realized that everything needed changing in the FP&amp;A team — the processes, the infrastructure, the systems, etc… There was so much to do but I prioritized and also synchronized all of the different tasks that had to be fixed. <a href="https://www.linkedin.com/pulse/key-building-effective-ecommerce-fpa-team-armstrong-mba-cma-cpa?trk=prof-post">I started with data </a>and then worked my way up to people and processes, then forecasting and business partnering — this order was important due to the critical importance of data in an ecommerce FP&amp;A team. In addition, all of these issues needed to be addressed in synchronization, because all of the fixes were necessary for us to be successful.</p><h3>4. Integrating into a large business should never be done half-way — standardize as much as possible</h3><p>Again in both crises, the finance and accounting infrastructure was never fully integrated into the parent business. Many finance and accounting processes were left as stand-alone operations apart from the parent. Duplication reigned everywhere, and it seemed like people were reinventing the wheel and/or doing things twice in many cases. Complexity was common.</p><p>Being a stand-alone operation also created a different way of managing the business. How the parent looked at its performance management was different than compared to the stand-alone business. Because of this isolation, powerful comprehensive systems were not taken advantage of to modernize operations, as most tasks were still managed within Excel. And there was no way to compare the stand-alone operation performance with other sister companies, so there was no ability to benchmark. As a finance leader, not being able to communicate in the same language as the other divisions to senior leadership was confusing and hurt credibility.</p><h3>5. It’s so important to focus the team to work only on value-add activities</h3><p>Trying to fix so many things at once required prioritization of the most critical and important tasks.</p><p>In both cases, I had limited resources to right the ship and so I focused on the foundation of the business (i.e. cleaning up the data) first, despite the fact that the business needed strong financial projections to make strategic decisions.</p><p><a href="https://www.linkedin.com/pulse/key-building-effective-ecommerce-fpa-team-armstrong-mba-cma-cpa?trk=prof-post">Fixing the foundation first</a> allowed the team to get to the value-add activities quicker instead of continually reinventing the wheel when we wanted to be effective in forecasting and business partnering. Getting to the value-add means you need to get the basics right first.</p><h3>6. Managing this crisis required a directive style of leadership — it was necessary for us to achieve our objectives</h3><p>Most technology cultures pride themselves on a consensus-building leadership style, which I firmly believe in. However in a crisis, this style could not be applied — we had no time to waste, as there were so many things to fix to ensure improvements. I needed to be firm and take charge in a crisis, as I understood the solutions that should be applied. This worked well … to a point.</p><p>Given my broad online ecommerce experience, I applied the best practices I learned to help standardize metrics, integrate systems, and automate processes in each of the crises. These best practices fixed the majority of issues however due to certain special product offerings and complexities, the best practices were not always “best” in each of the crises.</p><p>This is where consensus building from the team and other internal partners to determine the right requirements for the business was helpful to optimize the systems and processes that were implemented. Tailoring slightly different processes to really meet an organization’s needs was necessary to complete the FP&amp;A team’s transformation.</p><h3>7. Systems implementations take much longer than anticipated, especially at a large company</h3><p>In each crisis, I identified two main systems that needed to be migrated: moving the marketing transactional data from Excel to the organization-wide financial planning tool Hyperion, and standardizing metrics to include the right data. It was clear to both my team and I on what should be done, however the processes had to be changed significantly. Because so much institutional knowledge had left the business in the last few years, we understood why this was never entertained before.</p><p>Specifically on the metrics change, we created documentation where none existed, and applied it to multiple layers within the organization; we uncovered so many uses of these metrics which were not known to the majority of our teams. The near organization-wide access to financial metrics created an abundance of stakeholders and teams to work with — bureaucracy existed for a reason already, but it was also amplified in this case.</p><p>The best way to work with these teams was to continuously communicate with the leaders, provide updates and to ensure deliverables were completed. You can enable and accelerate the process if you know the right people to talk to — call them, talk to them and provide them the reasons for why this project is so important. This “greasing the wheel” will certainly help facilitate meeting the timelines.</p><h3>8. Hire a BI/Data specialist at the start of the transformation to help build reports and straighten out data flows</h3><p>Ensuring that data can be visualized or analyzed in a timely manner is very important in a data-driven ecommerce organization. Most financial analysts are not programmers who are able to write code to automate reports in Tableau or in Excel using macros. Asking these team members to do this type of work usually does not set the right expectation with them — having said that all analysts should have some macro skills for automation in Excel.</p><p>So in one of the crises, we wanted to hire for this skill-set in our team quickly as the reporting infrastructure was either broken or did not exist, despite the fact that FP&amp;A owned the financial correctness of the data. However this was difficult as the goal of the organization was to centralize all BI &amp; data specialists within the technology team to serve all the business partners. But when we as business partners weren’t served adequately, we were motivated to address this gap.</p><p>It took almost a year, but we finally hired our specialist and the streamlining of our reports and data flows have made all the analysts lives’ easier so they can focus on analysis as opposed to report building. IMHO, a BI systems person who manages requirements and processes are critical in an ecommerce FP&amp;A team — and should be the first hire.</p><h3>9. New motivated team members need time to understand the business — but they will get there</h3><p>In any crisis, you will be forced to ramp up your hiring. I hired staff in both cases and the people I put in place were both motivated and experienced but were still “rookies” on the job given the challenging environment.</p><p>This was a significant opportunity for these employees to build their personal brand internally within the organization to show what they could do. They had a fresh perspective wanted to add value by looking at problems differently to suggest new solutions — however, it was tough for them to contribute right out of the gate. They were thrown into the fire with little guidance and significant demands placed on them. But in the end, they made it happen.</p><p>Looking back on what we did, what the teams accomplished were monumental given the lack of experience they had. Over time, I saw that the more experience they gained, the better they performed. Have patience with motivated employees and they will succeed.</p><h3>10. My first crisis experience as “le nettoyeur” gave me the opportunity to do the same thing again in another crisis</h3><p>Realizing that the first crisis was an opportunity, when a similar opportunity came up again, I said I would jump in without hesitation. The same issues that I saw in the first case were present in the second case: I had to reorganize the team and apply the same rigor to fix the data, reports and processes in an interim role until a new leader came on board.</p><p>As an interim leader, you’re only able to fix so much: hire some staff, standardize reports, focus on key metrics, create forecast processes, etc… In this case, I provided the second FP&amp;A team as much guidance as possible to help them drive to the goals they needed to reach.</p><p>My personal brand has now been cultivated to be not just an ecommerce FP&amp;A “<em>nettoyeur</em>”, but one who can confront a challenging situation, determine the best course of action, and drive the team to achieve success. All because I was able to identify a crisis as an opportunity and had the confidence to turn it around.</p><p><em>Do you agree or disagree with the points made in this post? Please share your feedback by liking, sharing and/or commenting below — I would love to hear it as it will help me drive better insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6f05cb1742b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Key to Building an Effective Ecommerce FP&A Team]]></title>
            <link>https://medium.com/@mattarmstrong_68463/the-key-to-building-an-effective-ecommerce-fp-a-team-3e5635c92ad7?source=rss-24502ab8fec4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3e5635c92ad7</guid>
            <category><![CDATA[finance]]></category>
            <category><![CDATA[financial-planning]]></category>
            <category><![CDATA[ecommerce]]></category>
            <category><![CDATA[cpa]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Matt Armstrong]]></dc:creator>
            <pubDate>Thu, 05 Jan 2017 17:38:08 GMT</pubDate>
            <atom:updated>2017-01-05T17:38:08.682Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Today’s online ecommerce environment is ever-changing and ultra-competitive. A financial planning and analysis (FP&amp;A) team must to be able to partner with its business leaders and meet growth objectives while managing the complexity that an online world entails. Most models that are applied to build an FP&amp;A team address a structure, but do not prioritize its implementation. Based on my experience, I found that I needed to apply a model that helps prioritize data and reporting as the foundation so that the FP&amp;A team will be successful on delivering its vision as the trusted ecommerce business partner it strives to be.</p><h3>Case Study — Re-building the FP&amp;A Team at Hotwire</h3><p>I came to Hotwire in the spring of 2015 to manage its FP&amp;A team: my fourth division within 4 years at Expedia Inc. This was a fantastic career opportunity; however it quickly presented itself with significant organizational and functional challenges. Organizationally:</p><p>1. The FP&amp;A team was decimated — two team members out of five quit right after I took the job, there was no permanent team lead in my position for 6 months, and the CFO left shortly after I started</p><p>2. Business partnering was limited at best — none of the leadership team members had confidence in reported results and to them, the financial forecasting process “was the most broken process at Hotwire”</p><p>From a functional perspective, it didn’t get much better:</p><p>1. Hotwire Finance was loosely integrated with its financial systems — Excel was the tool to manage all of the historical financial performance with large interlinked files and no backups, while only final model outputs were uploaded into Hyperion (not making use of its modeling capabilities)</p><p>2. Metrics were inconsistent with the rest of the organization — there was no comparability internally across brands making Hotwire unable to leverage the corporate infrastructure</p><p>3. Scorecards were incorrect and unclear — business drivers were not broken out for visibility, while key dynamic assumptions were incorrect and hardcoded in the BI systems</p><p>4. Intercompany revenue share management was needlessly complex</p><p>These challenges all together represented a crisis and I needed to address them in a way that ensured the FP&amp;A team was set up for success in both the short and long-term.</p><h3>Why is FP&amp;A different in ecommerce? It’s simple: data.</h3><p>Today’s ecommerce business operates in a dynamic environment that creates a proliferation of real-time data. This data provides a significant opportunity for organizations to make decisions rapidly to react to customer trends, and drive business profitability.</p><p>Analytics teams were the first to take advantage of this data to develop leading operating indicators which helped direct the business’ product management and strategy. This is what led to the <a href="https://hbr.org/2011/03/a-step-by-step-guide-to-smart-business-experiments">“test-and-learn”</a> philosophy that has been the foundation for many internet platforms and helped explode the <a href="https://en.wikipedia.org/wiki/Data_science">“data science”</a> domain. FP&amp;A teams tried to follow suit to use this data to ensure it had a business view of profitability, but the traditional FP&amp;A processes, systems and skills were often ill-equipped to address these new challenges: they were slow, reactive, and linked leading to lagging indicators poorly. The ecommerce FP&amp;A team needed to change by really focusing on the most important criteria — <strong>data</strong>:</p><h3>1. Data is fundamental to the FP&amp;A function — without it, you’re lost</h3><p>At a technology infrastructure level, the massive amounts of customer data flowing through its shopping path captures product, channel, conversion and purchase data. This complexity creates a huge challenge to ensure valid and relevant predictive models across these multi-dimensional attributes. If not managed appropriately, the vicious cycle of garbage data-in, garbage data-out can lead to missed opportunities, masked expectations, and can <a href="https://econsultancy.com/blog/64612-the-cost-of-bad-data-stats/">significantly impact the bottom line</a>.</p><p>Compounding this complexity is that multiple views on the same data can create chaos — one version of the truth is necessary for management clarity and consistency, as data governance usually resides in finance to ensure this singularity. And there sometimes needs to be separate views of operational data and financial data — not being able to distinguish the two can add to this lack of clarity in decision-making.</p><p>Companies who rely on <a href="https://en.wikipedia.org/wiki/Big_data">“big data”</a> will be challenged to provide insights if they are not properly set up for data management; they will be flying blind due to its complexity and lack of organization.</p><h3>2. Ecommerce businesses operate in a rapidly-changing environment where real-time decisions are critical</h3><p>Having the speed to deliver is important to make timely decisions; ecommerce business environments can change rapidly due to the competitive nature of online marketplaces. Being set up for success requires being efficient in getting to the right information as quickly as possible — automating data processing and trend analysis are essential to solid decision making.</p><h3>3. Revenue and marketing cost modeling are critical to scale profitably, while capital investment modeling is less critical</h3><p>A major goal of an ecommerce business is to achieve scale with limited fixed costs. However to increase volumes, you need to manage the short and long-term trade-offs of the revenue from customer transactions vs. the costs of customer acquisition &amp; processing. Infrastructure investment is important to ensure the business keeps up with current technology, but it is relatively fixed compared to the variable nature of an online business, and can also be managed in a less time-sensitive manner.</p><p>Ensuring operating profitability can even be more daunting if revenue and/or costs cannot be recognized immediately, as estimates of future profitability are more variable requiring more and more granularity in the metrics.</p><p>Due to these underlying forces of the short feedback cycle in ecommerce, FP&amp;A needs to quickly generate insights from the transactional data, apply financial profitability metrics, ensure targets are met while resources are adequately distributed, and then adjust the forecast accordingly. At Hotwire, we had the challenge of not being able to address the ecommerce feedback loop in a timely manner due to manual data collection, incorrect scorecards, and inconsistent metrics management. It was fundamental to address these challenges as quickly as possible.</p><h3>The Pyramid of Ecommerce FP&amp;A Functions</h3><p>Given this perspective, I wanted to explore how I could apply these concepts to current FP&amp;A organizational models to ensure my team was set up for success. I found that models have been developed at the <a href="http://www.fpa-trends.com/article/london-fpa-board-fpa-analytics-maturity-model">London FP&amp;A Board</a> (more analytics-based), <a href="http://www.fticonsulting.com/~/media/Files/us-files/insights/featured-perspectives/rethinking-fpa-operatingmodel-whitepaper-v4.pdf">FTI Consulting</a> (service delivery for COEs), and at the <a href="http://www.afponline.org/publications-data-tools/reports/maturity-model">Association of Financial Professionals</a> (applied key domains of self-assessment). The most relevant for ecommerce I found was the AFP model; however I did not see an order of prioritization of its self-assessment domains. I knew that I wanted to scale my team’s FP&amp;A capabilities in data management first, given its foundational importance. This is where I created key functional FP&amp;A areas and prioritized them into a pyramid as follows:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*3BWQWityZLBgokLsKI718g.png" /></figure><p>This diagram shows that data needs to be firmly provided on a clean and consistent basis. Once that is done, I need to ensure that the right people are in the right roles to follow strong processes, as it will help automate the analysis of business performance trends. However, without proper data, a “rock star” talent won’t be able to proactively drive insights and/or meet expectations.</p><p>Next, the team can apply proper insights from the correct reports and processes to help forecast their product volumes, revenues and costs, as well as analyze business cases to develop promotions, release new products, etc.</p><p>FP&amp;A can then apply these analyses and forecasts to share in high-level business partnering relationships and drive the outcomes necessary for success. The pyramid guided me to focus on the foundations at Hotwire: first on data and reporting to ensure correctness, next to put the right people and processes in place, and then onto higher value-add activities such as forecasting and business partnering.</p><h3>Stages of Evolution within each Pyramid Layer</h3><p>Understanding where the team is capability-wise can help determine how to approach the team’s growth. Each of the layers in the pyramid has a range of competence, from novice to expert. Similarly, the <a href="http://www.cebglobal.com/">CEB</a> did some research at Newell-Rubbermaid that showed how specific core capabilities can progress from novice to expert levels. This type of leveling can be easily applied to the above pyramid model:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/759/1*-6cQ_tmr2rSHcSrYwqUlAA.png" /></figure><p>While building from the ground up, it’s important to note that a team does not need to be at an expert stage in a low-level layer before building competence in a higher layer. Depending on the complexities of the business, the skills within the team and the financial health of the organization, there may be a need to build functions vertically in sync. However, it is not possible to be an expert in one layer higher than another having lesser capabilities. For example, you can’t be an expert (or instead more advanced) in <em>business partnering</em> while being a novice in <em>data and reporting</em> because the fundamental insights needed for strong <em>business partnering</em> aren’t being generated to be shared with the business.</p><p>However, it is possible to be the opposite — an expert in a lower layer while still being a novice in a higher level, such as <em>analytics and forecasting</em>. Improvements can be made in forecasting because the foundations for success have already been laid. Building competence in each of the layers is non-trivial and takes time — do not assume that this can be done overnight.</p><h3>Applying the Pyramid at Hotwire</h3><p>At the start of my tenure at Hotwire, it was extremely challenging to have solid <em>forecasting</em> and <em>business partnering </em>discussions with the leadership team without having the necessary foundation in <em>data and reporting</em>. What we did was while straightening out this function, we hired the right <em>people</em> and ensured they were proactive to help the business — these new employees could then become familiar with the challenges and help address them while they became acclimated to the business.</p><p>Our <em>forecasting and analytics</em> capabilities are still limited due to the slow progress of our data management transformation, which included metrics correction, and migration of our data from Excel to Hyperion. However we have improved significantly given the clean-up we had to make by using interim systems and addressing our process gaps at the start. As such, the team is now more proactive: operating with more automated and repeatable processes due to integrated systems and better equipped to drive strategic value. Consequently, the business is now relying on the FP&amp;A team to drive insights and strategy for investment and growth.</p><p>Despite all that we have accomplished in over a year and a half we still have a long way to go. We must continue to strive for that trusted business partner role as it requires building on the foundations of each of the successive layers of the pyramid.</p><h3>Conclusion</h3><p>Transforming an ecommerce FP&amp;A team requires building in standardized functional layers on top of clean data and reporting. At Hotwire, I was able to rebuild our FP&amp;A team by prioritizing from the ground up on effective data management and reporting up to predictive analytics and forecasting in order to provide the indispensable insights to our organization’s leadership. As “big data” and <a href="https://en.wikipedia.org/wiki/Machine_learning">machine learning</a> begin to take over the internet, our FP&amp;A team not only will be well-prepared to address this challenge, but it will provide our business a leg up on its competitors.</p><p><em>Do you agree or disagree with this post? Please share your feedback by liking and/or commenting below — I would love to hear it as it will help me drive better insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3e5635c92ad7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>