<?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[Capital Letter - Medium]]></title>
        <description><![CDATA[Reflections and scrap notes from financing and building a high growth business at the epicenter of the (latest) tech industry froth. - Medium]]></description>
        <link>https://medium.com/capital-letter?source=rss----1173e14b9f7---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Capital Letter - Medium</title>
            <link>https://medium.com/capital-letter?source=rss----1173e14b9f7---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 08:48:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/capital-letter" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Where should your management dashboards’ reside?]]></title>
            <link>https://medium.com/capital-letter/where-should-your-management-dashboards-reside-56729b344677?source=rss----1173e14b9f7---4</link>
            <guid isPermaLink="false">https://medium.com/p/56729b344677</guid>
            <dc:creator><![CDATA[Martin Rannje]]></dc:creator>
            <pubDate>Mon, 25 Aug 2025 15:59:26 GMT</pubDate>
            <atom:updated>2025-08-25T15:59:26.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*lYUKCdLFtOKel0K4exPBPQ.jpeg" /></figure><p>As close to the source data as possible. If you have a choice between having your dashboards in Excel/Google Sheets, an advanced reporting or BI application or simply in whatever the source systems can provide, the answer is usually to keep it in the source systems. Why? a) To enforce as healthy data integrity as possible and b) to keep the consumption of the insights as accessible to the end-user as possible.</p><p>Data integrity in key “sources of truth” (typically at least your CRM and ERP/Accounting system) to be one of the two or three most important things I “worry” about in my job. This data is the source of most answers to business questions and hence foundational for decision-making. If it is unreliable, every week becomes a world of misery as questions are left unanswered and decisions are not taken, and trust in the data is gradually eroded.</p><p>Maintaining good data integrity is more a human question of process than a technical question of infrastructure or workflows. The latter helps, but without good recurring processes based upon reports from that data, it will eventually degrade in quality. No matter how good your system rules are.</p><p>When your dashboards reside in the source systems, you get two benefits:</p><ol><li>They are feeding directly off the data in the system and can usually easily be “opened up” or “drilled down” to understand exactly what is happening. Making it easier to build trust in the underlying data, catch errors etc.</li><li>They are often automatically accessible to the main users and producers of this data (whether those are in Finance, Sales, Marketing), in an environment they are used to seeing and using. So it’s natural to them and they also trust it more. So you are seeing the same numbers as the “frontline” people.</li></ol><p>When dashboards are moved out of the source systems, it’s usually for one of two reasons:</p><ol><li>The data needs some form of transformation that the source system cannot do on it’s own (e.g. an advanced cohort calculation or similar).</li><li>The system cannot produce the desired visual in the form of the right table or chart.</li><li>The data needs to be accessible to users that cannot possibly be allowed access to the source system (either for financial or compliance reasons).</li></ol><p>All can be valid reasons to move it. But you have to make sure you understand the trade-off against the benefits mentioned above you are incurring, as you do this. I have learned this the hard way myself.</p><p>So when someone approaches you with a request to have some form of advanced dashboard in any “non-source” system, ask yourself (and them):</p><ol><li>Why do we think this is truly necessary? Most source systems have standard reporting built in that is adequate for at least the core users. Why is our business unique?</li><li>Is this a common practice in other businesses, meaning there is already a standardized approach to do this that a lot of people are used to? If not, the risks of doing this will be higher.</li></ol><p>If there isn’t a compelling answer to those questions, at least park it for now and see if the problem/grievance is still there a month or 2 from now…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56729b344677" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capital-letter/where-should-your-management-dashboards-reside-56729b344677">Where should your management dashboards’ reside?</a> was originally published in <a href="https://medium.com/capital-letter">Capital Letter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Make finance strategically relevant]]></title>
            <link>https://medium.com/capital-letter/make-finance-strategically-relevant-49c750e6ac6d?source=rss----1173e14b9f7---4</link>
            <guid isPermaLink="false">https://medium.com/p/49c750e6ac6d</guid>
            <dc:creator><![CDATA[Martin Rannje]]></dc:creator>
            <pubDate>Wed, 23 Dec 2020 22:57:47 GMT</pubDate>
            <atom:updated>2020-12-23T22:57:47.441Z</atom:updated>
            <content:encoded><![CDATA[<h4>Build growth enabling capabilities</h4><p>For a fast growing technology business, 3 long term priorities typically take precedence over everything else: People, product and revenue. They are considered critical value drivers. If you head up finance at such a business, you have probably (hopefully) asked yourself how you can best contribute.</p><p><a href="https://medium.com/point-nine-news/when-should-you-hire-a-cfo-9e4abaaec05d">This note</a> by Jason Lemkin is a good starting point. I concur with most of those thoughts, but wanted to spend a bit of time sharing what I have found to work well to actually get to “great” in terms of building the right capabilities.</p><h3>The key functions of finance</h3><p>My experience is finance’s role can be summarized as:</p><ol><li><em>Protecting existing value</em>: control operating spend and cash, ensure compliance, manage risks etc. (“avoid bankruptcy” falls in this category…)</li><li><em>Adding new value</em>: optimize operations, inform strategic decisions, identify and evaluate strategic opportunities etc.</li></ol><p>The biggest pitfall I see finance teams fall in at high growth businesses is dedicating too much focus and resources to #1. The finance leader then becomes a “Chief Admin Officer” and the portfolio of tasks very back-office operational. In any strategic questions finance plays a reactive support role.</p><p>The work in #1 is foundational to a finance function, but if #2 is not prioritized the function will have left an incredible amount of value on the table and lost a lot of its’ strategic relevance. Your CEO likely spends 80% of his/her time on #2 and simply expect you to handle #1. In the end it even becomes an obstacle to the business itself because finance by definition owns a lot of the information required to take the right strategic decisions.</p><p>To avoid falling into this trap, this is what has worked well in my experience.</p><h3>1. Get into your CEO’s shoes</h3><p>Your CEO is your biggest customer so his/her mindset and priorities should inform yours. These are usually related to the 3 mentioned above, but you need to understand what it means for your business. If it’s a pure software or SaaS enterprise, it could be Go-To-Market drivers you should be focusing on. In a marketplace it could be all about supply chain or delivery etc.</p><p>The upshot to me is that finance teams, when asked to identify improvement opportunities, are inclined to focus on financial and operational efficiencies (e.g. cost savings) because they have a natural skillset there. But growth opportunities are much more important to a high growth business — whether that’s revenue or people. So this is where you should be looking first.</p><h3>2. Decide which problems you can solve</h3><p>Strategic problems and opportunities come in many shapes, but there are limits to which ones a finance team can realistically support or enable. E.g. my experience from the software sector is that most often commercial or GTM issues become the natural strategic strike zone for finance teams. It is just harder to contribute to product with a finance skillset.</p><p>To decide which strategic problems, processes or functions you should take ownership of, look for two properties:</p><ol><li><em>Pivotal skill-synergy</em>: Financial acumen, data-driven problem solving, process management or contractual skills are pivotal to drive solutions.</li><li><em>Pure cross-functionality</em>: The process or function requires consistent execution across several functions/teams to deliver full value AND can be separated from mission critical tasks in each team.</li></ol><p>Be mindful that for #1 those skills must be need-to-have, not nice-to-have. Data-driven problem solving is useful everywhere in a business, but it is not always an essential skill to solve the problem. The same goes for #2. A lot of processes exhibit some sort of cross-functional interfaces, but consistent cross-functional execution might not be critical (good hand-off points will do).</p><p><em>I cannot stress the importance of avoiding over stretching your team with too many functions. </em>That will have the opposite effect of making you strategically relevant. So use the criteria above to both scope your ownership “in and out”.</p><p>If the process or problem fulfills both the above, you should align with your CEO and critical stakeholders (e.g. other VPs or C-level execs) that your team should probably own it. If only one of them is true, finance could perhaps own it but it’s most often because “no-one else” had the bandwidth or skills.</p><p>At Cobalt.io this resulted in the following Finance team structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WGlQ7jyPTqFoJL59d8_-g.png" /></figure><p>I have been particularly satisfied with the level of visibility into the business performance RevOps ownership has given my team. But even deal desk has to me become a critical finance capability.</p><p>Of course these headlines are the ones we chose. There are other ways to categorize them (e.g. many tasks could be considered either FP&amp;A, BizOps or RevOps or Corporate Development). And the ownership might change as the business grows (at some point this might be too much in one function)</p><p><em>The critical point is that you must be able to assume ownership of the capabilities that make you a natural strategic contributor and business partner to the CEO.</em></p><h3>3. Build internal capital</h3><p>The last critical step is to establish you and your team as a trusted authority and natural strategic contributor, not just with the CEO, but in the whole organization.</p><p>It’s not enough to have established a team with the right skills and task ownership. You are dependent upon the goodwill of the entire business, top to bottom, every day, to get the information you need, ensure they seek your advice in significant financial and strategic decisions etc. And life is just so much easier when everyone’s collaborative because they expect that your work will make their life easier in the long run.</p><p>A culture of enablement must be the bedrock of your entire team — finance, ops, legal etc. People must view your team as a source of solutions and pragmatism, not a millstone around their necks. I believe this was my own #1 success factor in all my prior jobs (it was not skills…)</p><p>As with all culture questions, hiring, training, promotions and firing are your key levers. Good stakeholder skills are some of the first things I look for in new hires. Do not hire people who are unapproachable — not even for the very introvert tasks. Your team does not need to be natural socialites, but they must have the ability to successfully enter a collaborative context.</p><p>Lastly, you and your team will often end up in situations where you are arbiters or negotiators. Spend a bit of time teaching them how to do this properly. Check my reading list <a href="https://medium.com/capital-letter/the-leadership-library-abcae248d73e">here</a> for inspiration.</p><p>All of the above is easier said than done. And your team needs to figure out what the lessons mean in your business. The only way to discover this is by trial and error. And of course leverage your network and peers.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=49c750e6ac6d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capital-letter/make-finance-strategically-relevant-49c750e6ac6d">Make finance strategically relevant</a> was originally published in <a href="https://medium.com/capital-letter">Capital Letter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Leadership Library]]></title>
            <link>https://medium.com/capital-letter/the-leadership-library-abcae248d73e?source=rss----1173e14b9f7---4</link>
            <guid isPermaLink="false">https://medium.com/p/abcae248d73e</guid>
            <dc:creator><![CDATA[Martin Rannje]]></dc:creator>
            <pubDate>Thu, 10 Dec 2020 07:06:15 GMT</pubDate>
            <atom:updated>2020-12-17T07:28:48.455Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><em>“Not All Readers Are Leaders, but All Leaders Are Readers”</em> — Harry S. Truman.</blockquote><p>An employee recently approached me asking about useful books on management and leadership. It caused me to pause for a moment because I believe the discipline is too rich and context dependent to be put on formula or communicated fully in writing. In the end it’s a practice, not a study.</p><p>However, I decided to write this short piece anyways because I do believe reading can help you get smarter and more skilled in the discipline by:</p><ul><li>Developing “first principles” that serve as lodestars in your strategic and operational issue-resolution and decision-making</li><li>Developing frames or categories by which to organize the vast amount of information you have to evaluate in your job</li><li>Zeroing in on the highest order “questions to ask” to explore a new field, subject or problem.</li></ul><p>In this post I lay out a) how I evaluate/choose management literature and b) what I consider essential reading for any aspiring manager (of anything).</p><h3><strong>i. Everything is a remix — choose the right ingredients</strong></h3><p>All management thinkers rest either explicitly or implicitly on some form of philosophical tradition(s). I evaluate all management literature on how consistent it is with an empiricist, pragmatist philosophical tradition as espoused by e.g. David Hume, Karl Popper etc.. Simply because I consider those ideas to be fundamental to the success of Western Civilization.</p><p>The most important take-away from these authors is that human knowledge is flawed and must be treated with caution. The world is complicated, you can only know for sure what you don’t know, and should proceed accordingly. That means e.g. “grand scheme” visionary (or “big bang”) thinkers would never be interesting to me, although I am sure some have been successful historically.</p><h3><strong>ii. Get out of the ivory tower</strong></h3><p>When I evaluate authors, I search for a mix of academic and practical experience. It means they are rigorous and serious, but not stuck in the ivory tower. Academic thinking alone tends to yield thoughts that are so disconnected that they can be almost useless. Good examples of this mix are Andy Grove (Ph.D. and later CEO) or Nassim Taleb (option trader, Ph.D. and later professor).</p><h3><strong>iii. Gauge the “Lindy Effect” to weed out the fads</strong></h3><p>Management thinking is unfortunately riddled with fads, most of them useless (in my opinion). So my second criterion for selecting books has to do with their timeless relevance.</p><p>The so-called “<a href="https://medium.com/@samuelpedro1992/what-is-the-lindy-effect-3c1d6ec96a08">Lindy Effect</a>” argues that the value of ideas increases proportionally with the age of the publication. Put simply, if a book has been in print for 40 years, it can be expected to be in print (or “relevant”) for at least another 40. The longer an idea has been relevant, the higher the likelihood it will remain so.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/730/1*QxQWu3OQvyKE-bcxoyHXbw.png" /></figure><p>Hence, in the order of age, here are the 10 books I would recommend to anyone who wants to be smarter on “management” or “leadership” (with links to summaries).</p><ol><li>“<a href="http://www.library.fa.ru/files/Hayek-Individualism.pdf">Individualism and Economic Order</a>: The Use of Knowledge in Society” (Friedrich Hayek, 1948): This short essay is not really a ‘management theory’, but it lays out why planning and execution has to be decentralized to be successful. The tenets here are pivotal to some of the most fundamental building blocks of management - like delegation and accountability.</li><li>“<a href="https://www.rightattitudes.com/2017/02/21/the-practice-of-management/">The Practice of Management</a>” (Peter F. Drucker, 1953): This study was groundbreaking when it was released. It laid the foundation for many of Drucker’s messages, such as “a business exists to create a customer” and “management is a creative rather than an adaptive task”. It also popularized the concept of MBO.</li><li>“<a href="https://www.negotiations.com/articles/getting-to-yes-book-review/">Getting to Yes</a>” (Roger Fisher, William Ury, 1981): This is the only book on the list that deals with the problem of negotiation. It’s one of the classics in the field. I refer to it because of its’ analytical, cooperative and partnership oriented approach to negotiation. It might not be the right approach for all negotiations, but for most business dealings it is.</li><li>“<a href="https://medium.com/@iantien/top-takeaways-from-andy-grove-s-high-output-management-2e0ecfb1ea63">High Output Management</a>” (Andrew S. Grove, 1983): This is arguably the most important book on this list. It is a primer on how to manage processes and teams, based upon his production management experience at Intel. Intel’s number one competitive advantage has always been execution, and they can thank Grove for that. The book’s approach is to view every activity in a business as a process with an output to be managed. It is rife with practical guidelines on how to obtain managerial leverage, how to run meetings effectively etc.</li><li>“<a href="https://www.sebastienphlix.com/book-summaries/minto-pyramid-principle">The Pyramid Principle</a>” (Barbara Minto, 1987): I give this book to (almost) all new employees. The message is that all ideas should be structured as a “pyramid” under a single thought. Particularly in my team (Finance, BizOps etc.) the form of logical, structured thinking and communication is essential to success. And I honestly believe it can improve productivity in every function.</li><li>“<a href="http://goodbadstrategy.com/about-the-book/">Good Strategy, Bad Strategy</a>” (Richard P. Rumelt, 2011): This book struck a chord with me because of its’ focus on strategy as problem solving. The messages regarding the importance of problem definition, focus and simplicity are spot on.</li><li>“<a href="https://www.themarketingstudent.com/thinking-fast-and-slow/">Thinking Fast and Slow</a>” (Daniel Kahneman, 2011): I was introduced to this book when I did my MBA. At the time the author recently received the Nobel Prize in Economics. The book is both a fascinating study of the human mind and useful guide on how to use “slow” thinking to eliminate biases of the mind and take clearer, more logical decisions.</li><li>“<a href="https://www.nateliason.com/notes/antifragile">Antifragile</a>” (Nassim N. Taleb, 2012): Taleb outlines how organizations benefit who set themselves up to benefit from variation (or risk — particularly outlier events), instead of trying to eliminate it, win in the long run. It is a bit abstract and at times a bit too inspired by his life as an option trader, but it’s the only book I know of that espouses a general application of the concept of “optionality” to create stronger businesses.</li><li>“<a href="https://www.nytimes.com/2012/12/09/books/review/the-generals-by-thomas-e-ricks.html">The Generals</a>” (Thomas E. Ricks, 2013): This history book analyzes the management of the US Army from the WW2 foundation designed by George Marshall to the present. The thesis is that US military success rises and declines with a certain type of rational, consequential meritocratic leadership that reached its’ zenith in WW2 (“…in WW2, the firing of a general was seen as a sign the system was working”) . It’s a compelling description of good leadership values with ample historical examples.</li><li>“<a href="https://www.15minutebusinessbooks.com/blog/2018/03/07/great-at-work-by-morten-hansen-my-six-lessons-and-takeaways/">Great at Work</a>” (Morten T. Hansen, 2018): A practical primer on how to work effectively as an individual, in teams and how to strike the work life balance. The work is based upon the author’s academic studies and his time at BCG. Some of the simple rules like “do less, then obsess” and “Passion &amp; Purpose” align well with the lessons I have learned myself in my work life.</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=abcae248d73e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capital-letter/the-leadership-library-abcae248d73e">The Leadership Library</a> was originally published in <a href="https://medium.com/capital-letter">Capital Letter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why this blog?]]></title>
            <link>https://medium.com/capital-letter/why-this-blog-483bd681cee7?source=rss----1173e14b9f7---4</link>
            <guid isPermaLink="false">https://medium.com/p/483bd681cee7</guid>
            <dc:creator><![CDATA[Martin Rannje]]></dc:creator>
            <pubDate>Fri, 04 Dec 2020 22:00:19 GMT</pubDate>
            <atom:updated>2020-12-05T05:23:48.371Z</atom:updated>
            <content:encoded><![CDATA[<p>Why spend time on writing about high growth tech finance and management?</p><p>Well, I started the blog firstly because I like to write. I have an academic inclination that I regularly try to suppress in my professional work, but it means I like to form arguments and theses and discuss them.</p><p>Second, I needed somewhere to collect my thoughts. I spend a lot of time gathering knowledge to explore new problems faced by a startup or get better at solving existing problems. So what better place than to collect them in public where everyone else can also benefit.</p><p>Lastly, I believe thoughts and reflections are not worth much without practical applicability. And I feel like there is a clear gap here when it comes to the content on the internet. Most knowledge and “thought leadership” on the net is simply not actionable without further clarification. Hence I will try and make my thinking as clear and actionable as possible. For that reason, comments and questions are obviously also welcome.</p><p>Finally, to quote the most important Western philosopher of the 20th century: <em>“Our knowledge can be only finite, while our ignorance must necessarily be infinite.”</em> — Karl Popper</p><p><em>Martin Rannje — December 2020</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1WVsqQXROc8C6DAkjknDGg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=483bd681cee7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/capital-letter/why-this-blog-483bd681cee7">Why this blog?</a> was originally published in <a href="https://medium.com/capital-letter">Capital Letter</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>