Proud to share that Megrow just completed five years of successful Interim Management and Risk Consulting.
Most sincerely, we appreciate that you are and hopefully will be supporting a small, professional and independent business!
Noteworthily, it is great to have partners along the journey. Veromont in Switzerland, Acacia in Hong Kong, Dennis Bessant in Manila, Qalybrate in Malaysia and Covolve in Singapore.
Interim Management and Risk Consulting complemented by tailor-made Training are the core services of Megrow. These three pillars will remain essential to what we do.
You need an interim C-suite executive to lead a transition or a special project? Reto Brosi and his partners have a significant track record of getting the right things done well.
Struggling to see the value in ERM and frustrated with slow progress and high costs? Our main goal is to make your ERM-journey efficient and effective. We produce tangible, measurable outcomes with and for you.
Clients have repeatedly engaged us for trainings and workshops. Our training and coaching sessions combine solid knowledge with practical experience. We pride ourselves in adapting our training modules to your specific needs. Whatever we take out of our “drawers”, we adapt it to your circumstances and your specific training needs.
the birthday podcast
We have published a short podcast to celebrate Megrow’s anniversary. Click below to listen and watch. Thank you for leaving a “like” and some comments.
We podcast about ERM and other topics. Occasionally, we have guests on the show as well!
Please, subscribe to our channel. You can access contents from almost any internet-capable device at your own leisure time.
Just published the most recent episode of the Megrow podcast. I thoroughly enjoyed the conversation with Andreas Zell, the founder and owner of AKR Zell Consulting in Singapore. Specifically, we spoke about the future of the actuarial profession in Asia and how ILS can help to close the insurance protection gap.
Thanks for listening, stay safe and please subscribe to this podcast and stay tuned for the next episode.
You got all the intent, ambition and ERM-skills lined up in your company: and still you are struggling to get much further than the first few hundred meters of the proverbial ERM-marathon?
If that sounds familiar to your mental ears, then read on. In this post, I guide you over some of the well-known ERM-mountains to make your ERM-voyage more effective and efficient.
This blogpost is the third installment of Megrow’s new “3 minutes ERM” series, which we publish on YouTube, LinkedIn and on this site.
Over the past years I came across a number of perceptions about ERM. As the word implies, perceptions are an individual’s or a group’s impressions, thoughts, preference and views. Hence, it is important that ERM practitioners are aware of these perceptions and deal with them empathetically and professionally.
A random sample of perceptions:
(if you prefer a broader source of information, just google “useless enterprise risk management” and you will not be surprised)
risk management is about managing downside – where is the link to strategy?
a purely internal activity
does not generate sales
only the regulator and/or stock exchange care
red/amber/green plots do not really say anything meaningful
it’s all about filling up spreadsheets for the drawer
another exercise to feed off probabilistic black boxes
etc etc etc … you get the point
Regardless how much real and/or perceived truth lies in these statements, perceptions amongst stakeholders do exist and we must deal with them early, best in an anticipatory manner. As practitioners we have both the opportunity and the mandate to deal with these views professionally.
how to manage?
firstly, transparency and clarity about the expected tangible benefits of good ERM are key
secondly, be cognizant that different stakeholders have different expectations towards the outcome and manage these expectations
thirdly, the output of our work needs to match generally accepted quality standards
furthermore, customize presentation of results to meet different stakeholder’s interest, knowledge, and commitment to ERM
and last but not least, communicate the results of the ERM-related work to show the link of risk management to strategy, business plans and performance.
I hope you find my ponderings useful for your day-to-day work. The specialists within Megrow’s network possess a wide variety of skills to successfully and efficiently navigate ERM hurdles. You can contact us via the buttons below.
Enjoy whatever you are doing, stay safe, please connect with Megrow over LinkedIn and/or Twitter.
Actually, a strong risk leader has a capability that many superheroes lack: the CRO can deploy different key skills at different levels at different time points! The “standard” comic superheroine and -hero often comfortably dwell within the realms of their existing superpowers.
I have written about the base-line skill of a good risk leader in a number of previous posts. In this blog, I share my thoughts how a successful risk leader deploys different skills at different levels of impact and intensity during different stages of an organization’s ERM-journey. I refer to these skills as the “adjustable skill set”.
Risk maturity frameworks are an excellent tool to illustrate many aspects of ERM. Below is a condensed summary of the risk maturity concept.
I use the simplified framework as the baseline of my considerations. Specifically, the framework describes the x-axis of all the charts that I’m sharing in this post.
In case you are interested in more detail about risk frameworks, type “risk maturity framework” into the search window of your browser. You will end up on the sites of RIMS or AON / Wharton or Hopkins and many others.
I focus on those CRO skills that are needed at different levels for different stages of an organization’s ERM-journey. They complement the base-line skills such as the understanding of the value chain the organization operates along. I have written about some of the baseline skills in a previous post.
influencer: drive change when needed
architect: design the right framework
executor: get the right things done well
innovator: seek the new at the right time
During early stages of risk maturity risk leaders often need to influence and convince all stakeholders that an improved ERM and resilience approach is beneficial to the organization. Hence, the change agent or “influencer” is a key CRO skill at this stage.
The importance will diminish somewhat once the machine is up and running (level 2 and 3). However, once the organization aspires to progress towards level 4, another “thrust” of change can propel the organization forward accordingly.
A good ERM set-up is appropriate and adequate to the organization’s current and foreseeable circumstances and complexity. Hence, architecting is a crucial skill at the onset of an ERM-journey. Especially during stage 1, significant efforts go into “architecting” the right approach and pathway. This will successfully pave the way for level 2 and 3. The curve does not drop to zero, since the framework will evolve to support changes in strategy, advances in methodology and other circumstances.
ERM-methods are no secrets (ISO sells it for app CHF 100). Peer reviews, google-able tips and tricks are abundant and external service providers can supply certain parts of the framework. However, once the organization wishes to become a true, recognized leader, then innovation skills are a must. The innovative, sometimes disruptive mindset of a risk leader is in high demand the higher up an organization is and desires to be on the risk maturity ladder.
Once an organization’s ERM effort is out of the starting blocks, execution is key to generate an efficient and effective risk management output. The risk leader must quickly initiate and complete transition from “agreed concept” to “flawless implementation”. Good execution remains key throughout the entire journey.
Certain CRO skills, such as understanding ERM methodology, support the entire journey. In addition, strong risk leaders, deploy other traits at different levels of impact depending on the status quo of the organization’s risk maturity. Ultimately, the strong risk leaders know when to deploy which skill at which level!
I hope you find my ponderings useful for your day-to-day work. The specialists within Megrow’s network possess a wide variety of skills to make your ERM-journey efficient and effective. Contact details below. Enjoy whatever you are doing, stay safe, please connect with Megrow over LinkedIn and/or Twitter.
This micro post focuses on “risk appetite” and its relations to risk bearing capacity, capital efficiency and the corresponding safety margins.
a glass well used
I use a glass to illustrate the total risk bearing capacity of an organization. In a first step, we set the total capacity of this glass to hold liquid as the organization’s maximum risk bearing capacity. The Board and Management need to have a solid, quantitative view of this capacity. For simplicity’s sake, we omit considerations of buying a second glass or putting the glass into the second larger container.
In a second step senior management and the board decide how far up they want to fill the glass. In other words, how much risk will the organization take. Theoretically, anything between empty and full is a go.
the glass is full
On the other hand, filling the glass up the top is very efficient. However, several stakeholders, such as shareholders, credit rating agencies and/or regulators might take a view that the firm should leave some buffer. Just in case anything causes turbulences to the liquid in the glass. Hence, organizations would under most circumstances leave some capacity unused.
the glass is empty
Having said that, if the glass is (almost) empty, then the company is not taking any risks. Hence, the organization is excessively risk averse and/or dormant. In other words, capacity (i.e. capital) usage is very low. This, over the long term, is inefficient.
The beauty about this concept is its flexibility. Should the business environment be very favorable, companies can decide to “fill up” the glass, ie increase revenue. Vice versa, if the environment is challenging, the glass remains less filled. Efficient capital management would then ask for a smaller glass – that is a topic of another blog.
Thank you very much for reading this post. Enjoy what you are doing and stay safe. For any questions pertaining to Enterprise Risk Management, please contact Megrow over LinkedIn or Twitter or the coordinates on the contact page.
This post describes how to structure and populate a good risk register. I will describe the key components, how they interlink and the recommended information requirements.
the risk register – what is it?
When you internet-search the term “risk register”, plenty of examples and tutorials will yield. Often, these samples are very well presented, easy to comprehend and relatively simple to adapt to your organisation’s specific circumstances. Having said that, at closer inspection many of them don’t pass muster even for the smallest and minimally complex organisations.
The image below represents a sample of what you will find with an internet search:
has a clear structure
outlines a risk of possibly loosing key employees
assigns a medium impact to it
allocates responsibility to the HR department
and leaves room for more risks
So you might wonder what is missing. After all, a risk is identified, its potential impact is being considered, and somebody is assigned to the risk. All sounds good, or doesn’t it?
The good news is that risk identification has taken place in this imaginary organisation. Furthermore, all three statements shown in this example are valid statements. However, they need to be brought into proper context and quantified. Additionally, some key ingredients need to be added. Hence, it is highly likely that this organisation needs to upgrade the register to reap the benefits of good ERM.
The risk of “loosing key staff” – as shown in the table above – is a real issue for many organisations. However, the statement needs context and explanation.
what does “key” really mean?
how does the “medium” fit into the strategy/priorities of the organisation. In other words, what would “low” or “high” signify?
and finally, what is the duty of the HR-department?
The model risk register
Let’s leave this example aside and move on to the build-up of a comprehensive, clear and more tangible risk register. How does a good risk register look like? I focus on content and the key building blocks. IT-considerations and data analytics are the subject of a different conversation.
High Level Structure
The header describes the risk at sufficient level of detail. I call this the “ID” block.
Right underneath the ID-block we draw three vertical blocks. They encompass quantification, risk treatment undertakings and the respective outcomes. This is the “quant/mod” block.
In the blocks at the bottom we record and store important additional information, such as follow-up actions and access rights. I call one of them the “add-on” block and the other one the “gov” block.
Key components are:
A unique risk identification. This can be a number or an alphanumeric code; you can decide to use existing internal codes or just a plain integer. Both approaches have advantages and disadvantages.
classification: risks need to be grouped following a pre-determined nomenclature and structure. You can use your own one or you can follow the guidance of the respective regulatory body or any other system that is suitable. Important is to cover ALL activities that your company is undertaking! The classification should span 2-3 levels for easy grouping and identification. Going back to our example, level 1 could be “operational risk”; level 2 “human resource risks” and level 3 “staff”.
description: provide a basic description of the risk in free text form.
impact: qualitative comments pertaining to expected impact should the risk materialise.
And importantly, who is responsible for managing this risk.
“quant & mod” blocks
quant block 1
The block on the very left displays estimates of likelihood and corresponding severity should the risk under consideration materialise. These values – as the name implies – should be numeric. Best practice and knowledge must be applied when determining them. Preferably, a solid probabilistic model is used. Alternatively, deterministic scenarios might be used or past experience is taken as a reference.
Generic statements like “often” or “expensive” are easy to come up with. However, they are very vague. Hence, try to use quantitative statements as often as possible.
Having said that, it is crucial to be cognisant and explicitly note uncertainties associated with any projections (regardless of method) made in this section.
In a next step, benchmark the outcome against your organisation’s risk appetite to determine whether any treatment is necessary. This benchmarking is important to ensure that treatment efforts are spent on risks that really matter.
The middle block describes the chosen treatment actions in detail; furthermore, treatment costs are elaborated on.
quant block 2
The block to the right contains similar information as the one on the very left. However, all values and conclusions are recorded POST the mitigation/treatment efforts have taken place. Again, scale the values against the risk appetite. Furthermore, compare the outcomes to the actual cost of treatment. And lastly, note the the effectiveness and efficiency of the treatment.
These latter points are crucial. One needs to determine and decide whether the treatment(s) achieve their objectives and what the cost/benefit of the treatment is. For instance, if the treatment of a certain risk costs “1.25” to cure a non-recurring impact of “1”, then it is likely not worth the effort!
In our example we would have specified what we mean by “key staff”. Henceforth, it will be easier to assign a probability and an impact should that individual or team leave. As a mitigant, you can think about development opportunities, flexible work arrangements, incentives and other measures.
Certainly, the “ID” and the “quant/mod” blocks are the most challenging and interesting components of the risk register. Populating those blocks often leads to in-depth discussions and sometimes heated arguments amongst all the contributors. But it’s always interesting and often fun to travel this segment of the ERM-journey. Having said that, a risk register without the remaining two blocks is almost like a house without basement! Hence, I strongly recommend completing the bottom two blocks as well.
You need to determine how often you will review each entry. Some risks change very rapidly. Take Cyber, where the risk landscape evolves constantly. Hence, Cyber-related risks need to be reviewed very frequently. At the other end of the spectrum, certain operational risks (under most circumstances) evolve much slower. Hence, your organisation can review these less frequently.
The second component of the add-on block are considerations are about additional classifications. Whilst we have grouped risks already in the “ID” block, it is advisable to do some more classification at this stage. Highly recommended is to classify or rank risks according to impact on strategy and materiality. Importantly, you should generate a “top 10” list of the risks that really really matter to your organisation. I borrow a term from a global consulting company: McKinsey make explicit reference to “the company’s big bets”.
And last but absolutely not least: you need to establish linkages between individual risks should they correlate. This is key, even if the correlation at first sight appears marginal only.
And finally, some important “housekeeping” matters complete the register:
assign an “owner” of the entire risk register. This person/function is the overall owner of the risk register. Note though, that the owner of the register is (in most cases) different from the risk owner!
state the author of the current register (in smaller organisations, this might be the same person/function as the “owner)
add a version number, and a date(s) for upcoming general revisions
make reference to the register’s exact storage location AND, crucially
determine “access rights” and “confidentiality”; the challenge is to find the right balance between being transparent and inclusive, whilst keeping some key strategic matters confidential. For instance, in the case of a key strategic risk, most information, especially the treatment and the impact, might be kept strictly confidential.
the gist of it
In this blogpost, I describe the set-up and design of a functional and comprehensive risk register. Six interlinked core components make up a complete register. If you have questions, kindly contact us via the social media buttons below.
… volume and complexity of risks … increasing extensively …
2020 The State of Risk Oversight, NCS
… less than 20% of organizations view their risk management process as providing important strategic advantage …
2020 The State of Risk Oversight, NCS
I look at the these two NYS Poole messages with a lot of optimism. On one hand, the risk landscape is evolving. Hence, the management of new risks is a challenge and provides ample opportunity for ERM-professionals to deploy our skills.
Secondly, there is much more work to do in providing real strategic value to all stakeholders. This is a call to all of us to demonstrate the real value by embracing the forward-looking, strategic aspects of good ERM.
ERM has a bright future!
ISO 31000 – the ERM Gold Standard?
I’ve written and podcasted (see the embedded YouTube video) about ISO’s approach to ERM previously. In this post I’ll add more depth to my views and some practical considerations.
31000:2018 what is it?
ISO has updated its Risk Management framework in 2018. Subsequently, many institutions and practitioners have provided explanations and comments to the update.
In a nutshell, the ISO framework is
comprehensive, yet concise and understandable
free of guff and lingo
applicable to any organisation and industry
ISO 31000 places great emphasis on senior management involvement, the iterative aspect of good ERM and its strategic value!
I’m a fan of ISO 31000. Having said that, a few points need to be added:
The document states several times that risk management needs to be “comprehensive”. However, the actual term “enterprise risk management” is not used. Whilst this is not a big deal per se, I would have preferred if they would have used the “e” word – at least occasionally.
The standard is comprehensive and quite easy to understand from a structure, flow and vocabulary perspective. However, there is very little practical guidance as to the actual “how to”. ISO leaves that to the community. Maybe I should publish an “ISO 31000 – How To for Dummies” guide. In other words, if an organisation is new to ERM, this ISO document will likely not be of much help.
Having said that, the ISO guide is an extremely helpful tool to ensure one’s ERM-approach is really covering all pertinent aspects.
Another little niggle I have, is the omission of board of directors’ responsibility. The document clearly refers to “leadership by top management”. However, top management is not necessarily equivalent to a board of directors. Maybe I am nit-picking here, but this aspect is important. Good risk culture starts at the very top (not just the top) of any organisation.
It’s great that the standard makes explicit reference to “connectivity between risks”. Hence, one of the major pitfalls of silo-ed risk management is addressed.
Lastly, I wish ISO would have been a bit more explicit with regards to the “velocity of change” in the risk landscape. Having said that, they do explicitly mention “emerging risks”.
The ISO standard is a great checklist providing all the necessary ingredients to good ERM.
Megrow Consulting has completed several ERM-mandates in recent years. We contributed to relevant text books and know the standards (ISO and others) well. Most importantly, we have worked with customers through the big picture risk landscape all the way down to the tiniest minutia.
I have blogged about the roll-out of the COSO ERM update back in 2017. In 2018, ISO updated their well-known risk management standard, too. Since then, I’ve spent considerable time studying and using both standards. Hence, I now feel comfortable and confident to share my opinion about those two well-known ERM frameworks. In other words, bienvenu to the COSO vs ISO battle.
Specifically, my comments pertain to the ISO 31000:2018 standard and the “COSO Enterprise Risk Management, Integrating with Strategy and Performance – June 2017” edition. The latter being quite a “mouth-full”.
In this post I set the scene for my considerations and share some high-level, more general comments about each of the standards. The following instalments will contain more detailed elaborations and considerations.
Admittedly, I am an erstwhile COSO-fan who voluntarily turned more into an ISO supporter over the past few years. Over the course of this article I outline why I have changed my preference.
If you prefer to listen the audio version of this blogpost, click on the image below.
standards – why do we need standards?
The world is beautifully diverse, every company is different, and jurisdictions and regulations vary across the globe. Hence, why do practitioners need risk management standards in the first place?
Very strong arguments must be made in favour of standards:
activities and outcomes of ERM-work undertaken by different companies and in different locations are easily comparable on a like for like basis
standards set a common tone
standards set a baseline, i.e. no more need to explain the basics
practitioners and consumers of their work can focus on the outcomes and not the underlying methodology – particularly important for Board of Directors
and there always is the “best practice” argument and defence
Which standard ?
Risk management standards are commonplace for a long time. Auditing bodies, ISO, COSO, the IRM, RIMS, AS/NZS 4360 and many other institutions have issued and are updating RM-manuals and standards. For this series of podcasts, I will focus on the most recent releases of the ISO and the COSO standards, respectively.
ISO and COSO – A High Level View
Both standards are well known and respected globally. In the same breath, the two guides desperately needed an update. ISO brushed-up after nine years: they released the most recent version in 2018. COSO on the other hand, took 13 years to update. Their most modern publication now dates to 2017.
At first glance, the ISO standard got more comprehensive in its coverage whilst shrinking in size. This was achieved by moving certain parts to other standards and focusing more on principles and high-level frameworks.
In stark contrast, the COSO document is impressive in length, the executive summary already covers 16 pages. The most eye-popping change is the abandonment of the famous COSO cube. COSO developed something akin to a triple helix to describe their view of ERM.
At this stage of the “COSO vs ISO smack down”, the score is even.
The first thing I noticed when reading through the ISO 3100:2018 is the lack of the word “enterprise” almost throughout the document. Has ISO gone back to the bad old days of silo-risk management? I don’t understand this apparent lack of the “E”-word. Having said that, the ISO standard goes to great length and detail referring to the enterprise and its entity, so there is nothing to worry, it seems.
I have a great liking for fluff-free written and spoken communication. ISO scores VERY big in this department. Simple, short sentences. Very little lingo & if there is specific vocabulary, then it gets explained separately in ISO 73.
ISO updated its definition of “risk” to a more modern meaning. They now give attention to the up-side and the downside of risk (FINALLY). Their previous focus on classical hazard risk, which by default knows only down-side, was a serious detractor to use ISO in a strategic and entrepreneurial context. I emphasise that proper management of hazard risk is very important, but ERM is so much more than that. The 2018 update emphasises more on strategic aspects of risk. In addition, it repeatedly calls the board of directors and senior management to duty.
ISO 31000:2018 focuses on principles and guidelines for ALL risks faced by any entity. On the flipside, the ISO document is rather generic and provides very little, detailed guidance for practitioners. That is a fair point of critique, however basic principles are – by the very nature of the term – generally applicable. The customisation to an industry, company-size and other idiosyncrasies is best left to the practitioners. In addition, regulators, trade bodies and other stakeholders often prescribe certain ERM standards, so the localisation is taken care of by other institutions.
When I set out as a full-time ERM-pro, I was immediately drawn to COSO. The main attraction was the strong link to business, opportunity risk and strategy. Almost like love at first sight.
My miss-perception that ISO is all about sequential processes that provide no entrepreneurial freedom and dictate compliant business almost how to sharpen their pencils added even more oil into the fire. Going through an ISO 9000 certification many many moons ago didn’t help either.
the “TRIPLE HELIX”
COSO abandoned their famous “cube” and developed something akin to a triple helix. The new shape is supposed to be as comprehensive as possible and depict the entire value chain. I give COSO a lot of credit for having the courage to defect one of their key “trademarks”. Having said that, the new triple helix appears to be too much of a good thing. It reminds me of the myriad of physicists who try to develop the unified “world formula”. This endeavour is a great thing. However, how many people will truly understand it and how practical is it?
The new COSO framework has the dimensions of a study textbook. Kudos for being that comprehensive. The illustrations look contemporary. However, I have a strong preference for a shorter and crisper version, something like the “core” ERM-approach. The more elaborate considerations, together with examples could have been published in a separate “book”.
COSO’s approach is very comprehensive. New risks, such as the ongoing development of technology and the ever-increasing connection between risks take an important spot in their framework. Furthermore, I like the ongoing emphasis that ERM is linked to strategy and performance. And lastly, COSO published a separate document delving into practical examples. Sadly, this compendium comes at an extra cost.
I give COSO a lot of credit for their (attention dear listeners: guff alert!!) reach-out to stakeholders through various channels. The authors and publishers released a comprehensive Podcast series, e-distributed brochures and set-up a YouTube channel.
Having said that, the executive summary that reaches almost 20 pages (with all due respect and consideration that COSO needs to give to various stakeholders) is a detractor. Depending on the format you choose, the COSO executive summary is about half the length of the entire ISO 31000 standard.
COSO vs ISO: THE VERDICT
After round one of the COSO vs ISO smack-down my score is as follows: taking conciseness, guff-free language and strong focus on general principles and guidelines into account, my verdict after round one is clear: “GAME and SET for ISO”. Bear in mind though, the match isn’t over yet!
Stay tuned for upcoming editions of the Megrow blog, in which I will take this COSO vs ISO contest into the next rounds. In the meantime, if you have questions about ERM or would like an outside-in-view at your current or planned ERM-efforts, kindly contact me via the links at the bottom of the page.
Several listeners have asked me to talk about the technicalities of podcasting. This blogpost summaries my approach of preparing, recording, editing and publishing the Megrow podcast. As a general rule, I strive to combine a decent quality outcome with the use of relatively modest hard- and software. Note though: many roads lead to Rome!
This blogpost is the (almost) verbatim script of the recently released Megrow Podcast Episode 5. If you prefer listening to it, click on this link or the image just below. Otherwise enjoy the reading.
You do NOT need to spend thousands of dollars on high-tech equipment or rent a professional studio to record a podcast at decent quality. However, some good equipment is needed to produce professional podcasts. Nothing worse than high quality content that loses its impact due to poor recording and shoddy processing!
A decent quality microphone is the single most important investment to make. Almost any external microphone is better than the built-in microphones in your laptop / tablet / PC / mobile phone.
I purchased a Yeti Blue, for around USD 130, because
all the reviews I read, attested the Yeti a very good sound quality
the price, whilst not cheap, felt reasonable
it connects via USB to any computer
no additional hardware, like sound mixers, needed
simple plug-in and record, no need to install apps or software
both the microphone and the stand feel very robust
micro can be adjusted for solo podcasting or interview-type conversations
and, I do like the design and the colors
The detailed technical description of the microphone and the color choice is available on the Yeti website. The Yeti is NOT a light-weight!
I also invested 20 USD into a pop-screen. When buying one, make sure it is big enough to cover the entire microphone. Make sure the lock comes with mounting clamps or screws to fix the screen on your mic or the table/stand that you put your recording gear on.
Both iOS and W10 have built-in voice recorders. They work perfectly well for podcasting purpose.
Important: regardless of the device/app you use, make sure it can record with at least 44.1 kHz sampling rate. Most apps have a “setting” or “preference” option where you can adjust audio quality to “maximum” or whatever the terminology of your preferred OS is. 44.1 kHz records sound at excellent quality whilst keeping the audio files at a manageable size.
One thing to note: when using a good quality microphone at 44.1 kHz settings, be absolutely sure that you record in a quiet environment to avoid picking up background noise. Our brains are excellent at filtering out low level noise emanating from air conditioners or cooling fans of computers. However, a good microphone will register fan noise, which will distort your recording. Hence be wary of “silent” noise when recording.
One additional point to note, especially when your recording device runs a different OS than your post-processing device(s). You need to record your audio in a format that the “receiving” OS and software can open and process.
Once you have recorded your ramblings, you may want to do some post-processing to enhance the messaging of your podcast.
Depending on the operating system you use, different options (at no extra cost) are available for editing your recordings. I mostly edit on a W10 machine using DaVinci Resolve 16 from Blackmagic. This editor is extremely feature rich, requires a journey along a steep learning curve and is available as a free download from the Blackmagic website. I use DaVinci because I grew reasonably familiar with it during the early days of my personal YouTube channel.
On the side: iMovie on your Mac will do the job just as nicely.
A voice-only editor is insufficient for me, because I add images, titles, lay-over text, video snippets and music to the voice recording.
Thus far, I’ve had a smooth journey in terms of finding content. I do a lot of Enterprise Risk Management consulting work, hence ERM is a given topic. Let’s hope the creative vibes stay with me for a long time!
I could easily record an entire podcast episode without preparation. However, I prefer to script each episode at great level of detail. Putting my thoughts on paper (aka MS Word) forces some discipline into my thought process. In addition, a script eases content management and instills more focus on the actual delivery. Reading off a script also makes recording quite straight forward.
And lastly, I release an accompanying blogpost on the Megrow website concomitantly to the podcast. The blog is a very close copy of the actual podcast script, so very little work is needed to cover two communication channels in one go.
Episodes usually last for about 10 minutes. I believe that 10 minutes provide enough time to get some detailed content across without “hand-cuffing” listeners for too long.
Once I have an almost final version of the script, I choose the “read-aloud” function in MS Word for proofing. Listening to the computer voice whilst following the text is such an efficient way of spotting mistakes and errors. Additionally, I also record the time needed for MS word to read the entire text – just to make sure I stay within the ten minutes target duration.
I’m obviously not a native English-speaker, so spell- and grammar check is a given.
Once I’m OK with the script, I set up the recording hardware. Mostly, I just put the laptop on top of a cardboard box, place the microphone next to it and fit the pop-blocker in front of the Yeti. It might not look very professional, but this set-up is fast and practical. For best sound quality, the Yeti needs to stand vertical and you need to talk into the microphone from the front.
I record each episode in chapters. Recording in slices makes the process much easier. When I stumble over my own words, I can simply discard the current chapter and re-record it. In addition, bite-sized audio slices also speed up my editing workflow.
My editing process is relatively straight-forward:
set the editor – DaVinci Resolve in my case – to 1920×1080 Full HD resolution. This is currently the best choice when considering file size and quality
match quality setting of the audio track in your editing software to the high-quality settings used for voice recording
add opening screen, the intro and the outro from my templates stock. The intro and outro form the boundaries of the podcast in the editing software’s story line
mark chapters in the podcast with distinct titles for easy navigation
add images, URLs and video snippets when needed
pre-view the episode a few times for final quality control
export the project at full HD and upload to YouTube
Recorded and edited, how will the world find your podcast and listen to it?
The state-of-the-art publishing process encompasses publication on one of the well-known Podcast feeders, such as Apple Podcasts or “Podcast Addict” for Android (to name just two). I was initially considering going down that route as well, but after a bit of thinking and tinkering, I decided to simply publish the Megrow podcast on YouTube.
YouTube has a very distinctive set of advantages
it is a very well-known, easily accessible and omnipresent platform
tagging and onwards distribution/linking to other Social Media channels is easy
I’m familiar with the platform
listeners can subscribe to my channel and post comments
show notes can be added easily
device and platform independent, only needs a browser
My current method of reaching out to my audience is a five-pronged approach:
post on YouTube
announce the Episode on my Megrow Twitter account
put the link on Megrow’s LinkedIn page
post link on “my” LinkedIn page
publish the (almost) verbatim podcast on Megrow website as a blogpost.
I hope my thoughts will be helpful to some of you who are current or aspiring podcasters! Thank you very much for reading this blogpost. Other blogposts are here. You can contact me via the buttons at the bottom of the page.