Brian Hiatt, Chief Information Officer, answered on 2018-10-17T17:46:54.283Z, 6 months ago
My board experience has primarily been with board members that are not technical. The approach I take is to "translate" technical bits into business impact information. It seems many non-technical board members care most about how to improve the business, not what is driving the improvement.
As an example, if I am requesting approval for a workload migration to public cloud (AWS/Azure) I keep all the technicalities out of the presentation and focus on business impact. Ie. Increases in revenue opportunity, cost savings, safety/security, positive impact to existing and future clients, and positive impact to internal departments such as Sales, and Finance.
I always include a business level discussion about compliance, risk management, and security as this seems to be top of mind.
In summary, skip all the technical details, translate into business benefits. After all, if there were not any business benefits, should you be doing it?
This takes a significant amount of thought and planning and if done, you as an IT leader will reap the benefits of a better board relationship, more "approvals" to proceed with projects, and the opportunity to grow your professional skills. It does work!
Farid F. Nagji, Managing Director, answered on 2018-10-17T18:16:33.177Z, 6 months ago
The approach you've taken makes sense. I have found you only bring up technical aspects along with risk management items in an Audit committee session if asked, otherwise it has to be short and precise and focused on business benefit.
Gary Donnelly, Chief Technology Officer, answered on 2018-10-18T04:41:25.128Z, 6 months ago
I read a recommended book a long time ago called the Pyramid Principle. Not only did it help me remove the technology speak it focus quickly on the outcomes working backwards through the details only if required.
Trilochan Parida, CTO, answered on 2018-10-18T06:31:19.966Z, 6 months ago
I am CTO & co-founder of Bookingjini, rest of my co-founders are from sales background, so my approaches is same as @Brian Hiatt. I always try to convince them through the revenue & business benefits. So you should try this approach to get approval.
Wayne McGurk, Ex-EVP, CIO at MoneyGram International, answered on 2018-10-20T16:37:01.825Z, 6 months ago
First and foremost, the board is responsible for driving shareholder value. Consequently, the intricacies and complexity of technology, in most cases, eludes them. For the most part they are users of packaged technology (i.e. email, on-line banking, smart phone apps, etc). Consequently, I try to relate complex technology to their everyday experiences. For example, I was attempting to describe a synchronous architecture to a asynchronous architecture. The example I used was an orchestra. Listening to a synchronous orchestra was like listening to each instrument play their part one at a time; one finishes the next begins until the piece is played. An asynchronous orchestra is like listening to all the instruments at the same time; the instruments are blended together until the piece is done; which is alot faster and less boring. The board instantly understood the complexity of what we were doing and why were doing it. The same applies to information security. Boards are keenly interested in following security because of the reputational harm it can have to a company when "bad stuff" happens. When talking about how data is protected,I talked about concentric circles of technology that detect or stop intrusions from occurring. At the center I always put the company's logo. The point that I drive home is one of defense in depth. So the long and short of it is that you have to know your audience and explain technology to them in a way that they use technology in their everyday life.
Kathy Keating, CTO, Apostrophe, answered on 2018-10-20T16:42:21.432Z, 6 months ago
When I present technical aspects to our board I always do it within the context of our Goals and the Metrics we're using to reach those goals. Any product feature I talk about within this context is described from the user-experience perspective and I talk about it as an "experiment" that we building to attempt to drive the metric in the right direction toward the goal.
I will only discuss architecture, technology choices, etc only when asked by a board member.
Paige Francis, Associate CIO, answered on 2018-10-20T16:49:50.711Z, 6 months ago
Most boards are non-technical but I’ve found they want to understand. Take a step back and, as you are planning your report out, keep the discussions high-level (but be ready to dive deep if asked questions) and tie the changes or direction in with business objectives. Also, detail ‘the why’ with each bullet-point. Example, moving email from on-prem to O365. It’s a move of efficiency, less to physically manage and replace in a lifecycle, freeing up people and fund resources moving forward, more manageable security, easier transitions in the future. At the end of each report, be sure to ask questions – does that makes sense? may I clarify the value? Each topic needs to be in layman’s terms with a direct connection to the business bottom-line. At the end of each presentation be sure to ask for feedback – either right then or provide a contact for future feedback – “It’s important to me that what I speak with you about holds value. If you have advice on how I might do this better, please don’t hesitate to let me know how I can deliver this in a more useful way.”
Stephen McKain, CTO, answered on 2018-10-20T16:55:23.361Z, 6 months ago
I need more info on what your board experience is like. Are you at liberty to share? If they are non technical then do you even need to present at the board meeting? Boards are supposed to advise , so how can they advise the CTO if they are not technical? I am happy to advise you with more detail of your experience.
Linda Brady, IT Executive, answered on 2018-10-20T17:01:45.89Z, 6 months ago
Provide explanations without any techie talk. Concentrate on what will happen as a consequence if you do not proceed as you are recommending. Explain external forces that require you to do whatever you are recommending. Provide stories that show how your project helps support the business. Provide metrics that show how you can provide a return on the investment you are asking for. Show how a known competitor either benefited or suffered by taking the same path. Remember they only care how your project benefits the company or the share price. Happy to discuss more details in person.
Ratindra Pande, CMO, answered on 2018-10-21T12:17:26.143Z, 6 months ago
A non-technical board understand things in this particular format:
What are you proposing? Does it reduce the overall cost? Does it improve the efficiency? Does it bring anything positive to the public face of the company? How much time required for full implementation of any solution/advice that you are giving?
If you know answers to all these questions then approach the board with proposals circling around these questions and keep the technicalities only to bare minimum, because somebody who hasn't gone through the technical language in his/her whole life, is not going to do so now either.
Michael Wahl, Senior Director of IT, answered on 2019-01-12T02:11:51.731Z, 3 months ago
Eric Prosser, Director of IT, answered on 2019-01-22T20:34:37.593Z, 3 months ago
Todd Dekkinga, VP of IT, answered on 2019-01-28T19:10:00.494Z, 3 months ago
GET THE MOST OUT OF PULSE
I am increasingly having to present to our board and it’s not always the best experience. Do you have any advice on how best to approach a company board that is not technical at all? - Pulse Q&A