<?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 David Knott on Medium]]></title>
        <description><![CDATA[Stories by David Knott on Medium]]></description>
        <link>https://medium.com/@dkoysta?source=rss-4555b5c11075------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MxwpXKV6I1xPRzV0jYvyNw.jpeg</url>
            <title>Stories by David Knott on Medium</title>
            <link>https://medium.com/@dkoysta?source=rss-4555b5c11075------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 18:26:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@dkoysta/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[Zang Jing Ge: The Way of the Architect]]></title>
            <link>https://medium.com/@dkoysta/zang-jing-ge-the-way-of-the-architect-6cf24e1c55f6?source=rss-4555b5c11075------2</link>
            <guid isPermaLink="false">https://medium.com/p/6cf24e1c55f6</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[hsbc]]></category>
            <category><![CDATA[strategy]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[David Knott]]></dc:creator>
            <pubDate>Sun, 10 Nov 2019 16:09:41 GMT</pubDate>
            <atom:updated>2019-11-10T16:09:41.302Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Architects are Strange</strong></p><p>The job of IT architect is a strange one.</p><p>Many people don’t really know what IT architects do (I’m pretty sure that I have never given a convincing account of my job to my non-technical friends and family).</p><p>Even fewer people understand what makes one architect better than another.</p><p>But every team knows when they’ve got a good one: problems seem to get solved quicker, decisions seem to get made faster, and the team has someone to turn to when they have questions like ‘How in the world does that work?’ or ‘How on Earth are we going to get it to do <em>that</em>?’</p><p>In the HSBC Technology team we believe three things about architects.</p><p>First, we believe that, whatever architects do, and whatever makes them great, we need more of them.</p><p>Second, we believe that we have figured out at least some of the features of great architects.</p><p>And third, we believe that these features can be learned.</p><p>There are many things which make a great architect (including 13 advanced leadership behaviours which I will share in a later blog post), but we have condensed them into three important dimensions: technical excellence; communication mastery; and leadership power.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*4PwrQ6KSEuAmA03y" /></figure><p><strong>Technical Excellence</strong></p><p>Since we first dreamt up the idea of an IT architect, and since the earliest days of enterprise architecture people have worried (and introspected, and blogged, and argued) about whether architecture in enterprises is a business discipline or a technical discipline.</p><p>As a result, for a good few years, it was possible to get away with calling yourself an architect with no greater technical skills than PowerPoint and Excel.</p><p>It’s very clear to us that this way of thinking is over. The modern world is built from technology, there is serious work to do to figure out how put this technology together to solve problems, build businesses and serve customers, and it is the job of architects to do that work. This job has only become more urgent (and more fun) as the range of technologies available to us has proliferated.</p><p>We expect every architect in the organisation (up to and including me in my role as Chief Architect) to seek and demonstrate technical excellence.</p><p><strong>Communication Mastery</strong></p><p>Paradoxically, the stereotype of the PowerPoint architect has long co-existed with the stereotype of the architect as a deep-thinking technical expert whose advice would surely be invaluable if only we could understand it.</p><p>We believe that this type of architect is not doing the job properly. There is no point in having the greatest ideas in the world if no-one else knows about them: the job of the architect is to get their ideas out of their own heads and into the heads of other people.</p><p>Communication is essential in all companies, but at HSBC it is especially important. We have over 220,000 people working across 66 countries, and our architects need to get their ideas to every corner of the organisation. This is a never ending job which needs energy and attention.</p><p>We expect every architect to develop and practice their written and spoken communication skills, and to communicate continuously and habitually.</p><p><strong>Leadership Power</strong></p><p>It might seem odd to talk about leadership in the context of architecture. One of the good things about being an architect is that you can normally get your job done without directly managing large numbers of people. (I run one of the smallest functions in Technology — less than 150 people — and even my architecture practice, comprising all the architects across the Technology organisation, is less than 1,000 people. Some of peers run teams of eight to ten thousand people.)</p><p>However, leadership doesn’t mean managing huge teams of people: leadership (especially for architects) means getting people to follow you, regardless of organisational hierarchy.</p><p>It’s not strange to emphasise leadership for architects: architecture is a leadership discipline.</p><p>Architects need to translate ambiguous, open-ended problems into solutions which people can follow, they need to take decisions and convince people to stick to those decisions, and they need to encourage people to keep going when the going turns out to be harder than expected.</p><p>In many organisations, architects fall back on governance and controls to force people to do what they want, but if they rely exclusively on these methods they are failing to lead.</p><p>We expect every architect to be a leader, and to derive leadership power from their skills and behaviour, not from their position in the hierarchy or governance authority.</p><p><strong>Giving it a Name</strong></p><p>So, we believe that great architects have technical excellence (the ability to take good design decisions), communication mastery (the ability to get other people to understand them) and leadership power (the ability to get people to follow them).</p><p>That’s a bit of a mouthful, though, so we decided to come up with a name that embodied these attributes. We ran a competition across the Architecture Practice, and Ming Jin, our Chief Architect for Risk came up with a name and concept that fit the bill: <em>Zang Jing Ge</em>, the name for the inner sanctum of a Chinese temple, where the scrolls of power are kept. In Kung Fu films and literature, Zang Jing Ge is the place the hero goes to learn new skills and level up.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/0*ZfvXtwlbn89Vqhlv" /></figure><p>For us, an architect reaches Zang Jing Ge by achieving technical excellence, communication mastery and leadership power.</p><p>We recognise that achieving Zang Jing Ge is hard, if not impossible. Every architect (including me) needs to work continuously to improve their technical, leadership and communication skills. We use our Technology Academy to help, with a training programme ranging from basic technical skills and introductory design thinking, through our Unicorn programme for people starting out as Solution Architects, to advanced training and coaching, such as the Leaders for Teachers course provided by HSBC University.</p><p>We think we know what architects do, we think we know what makes a great architect, and we’re working really hard to help people become architects, and to help our architects become great.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6cf24e1c55f6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[There’s No Nostalgia Like Computing Nostalgia]]></title>
            <link>https://medium.com/@dkoysta/theres-no-nostalgia-like-computing-nostalgia-bf6b8a1e0e8c?source=rss-4555b5c11075------2</link>
            <guid isPermaLink="false">https://medium.com/p/bf6b8a1e0e8c</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[hsbc]]></category>
            <category><![CDATA[computing]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[David Knott]]></dc:creator>
            <pubDate>Thu, 11 Oct 2018 13:15:25 GMT</pubDate>
            <atom:updated>2018-10-11T17:40:58.975Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>I Wish I’d Kept My Acorn Atom</strong></p><p>I learnt to code in BASIC on an Acorn Atom (a British microcomputer) when I was 12 years old, in 1980. I had been pestering my parents for months to buy me a computer (learning BASIC from books and trying to imagine the programs in my head wasn’t really cutting it). Switching on the machine in all its 12KB glory, (along with a portable black and white TV and a cassette tape recorder) and seeing the cursor awaiting my commands was a powerful experience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/883/0*J33CU40PklPxn_BB" /></figure><p>Why does this experience from the dawn of my career matter today, though?</p><p>In the HSBC Technology leadership team, we believe that everyone should remain a hands-on technologist, no matter how senior they get in the organisation. We also realise that this has not always been the case in enterprise IT teams: for many years, the more senior people got, the more distant they got from technology, and the more they focused on managing people, finance and processes. And we realise that this is as true of us as of most people in our profession.</p><p>In our ongoing campaign to rediscover our technical roots, we recently conducted a simple exercise. We all shared our first Command Line Experience (CLE): the first time we entered instructions (of any form) into a computer (of any form) and got it to do something. We shared the year our first CLE took place, our age at the time, the machine we were using, and the language we used.</p><p>My first CLE was the moment I describe above: turning on the microcomputer that was going to occupy much of my waking time for the next few years.</p><p>Across twenty one people (it’s a big technology leadership team for a big company), we got some interesting results.</p><p><strong>Formative Computing Experiences Were Universal</strong></p><p>First, everyone had had a CLE at some point in their lives. This was slightly surprising, as the team includes people from Legal, Audit, HR, Communications and Finance functions. But it was great to find out that there was a proper technologist there somewhere in everybody.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*3_4n6guBFr_JI9A1" /></figure><p>Second, although the experiences covered a big span of time — twenty five years from 1976 to 1991 — the age at which most people started was fairly consistent. The earliest start was at nine years old; the oldest was at twenty two; but most people got their start in their early teens, between eleven and fourteen.</p><p>Third, those twenty five years fell into three distinct eras: before 1980, when people mostly learnt on time shared mainframes, such as the Honeywell H200, the ICL 2900 or the Sperry Univac; from around 1980 to 1990, when people learnt on individual microcomputers, such as the Commodore 64, BBC Micro and Apple II, usually in BASIC; and from 1990 onwards, when people mostly learnt on PCs, and technologies such as Dbase and the first indications of the Internet era such as HTML appear.</p><p>Fourth, up until the PC era, most people had vivid memories of the exact model of machine they learnt on. Once into the PC era, everything got blurred into ‘just another PC’. Those early machines seem to have had a lot more personality.</p><p>However, the most important finding was when we turned from the facts of our CLE and considered our emotions: how we felt at the time, and how we feel now, remembering the experience.</p><p><strong>Nostalgia is an Energy</strong></p><p>The feelings at the time (if we can trust our memories) were universally of excitement, a heady feeling of control that we could get a sophisticated machine to follow our instructions, even if those instructions were trivial. There’s a reason that ‘Hello World’ persists: aside from being simple, it’s a signal that we have some sort of control of the technology in our hands.</p><p>The feelings now were of nostalgia, and an itch to open up a text editor or a terminal window and get something done. It was a reminder that, whatever management tasks take up our days, we got into this field because we enjoy technology, and because computers are fun.</p><p>As well as remembering our first CLE, we also all committed to find our next CLE: the next opportunity to put ourselves back at the command line using the current generation of technology, to ensure that we are correcting the drift of decades away from a focus on technology and towards general management.</p><p>We are still managers and leaders: our jobs are still to manage and lead people and processes as well as technology. But our ongoing enagement with the command line will make us better at those jobs — and make them more fun.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bf6b8a1e0e8c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Two Lessons About Lessons]]></title>
            <link>https://medium.com/@dkoysta/two-lessons-about-lessons-1f583bf2580e?source=rss-4555b5c11075------2</link>
            <guid isPermaLink="false">https://medium.com/p/1f583bf2580e</guid>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[banking]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[hsbc]]></category>
            <dc:creator><![CDATA[David Knott]]></dc:creator>
            <pubDate>Thu, 04 Oct 2018 06:27:19 GMT</pubDate>
            <atom:updated>2018-10-04T06:27:19.014Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Leaders as Teachers, Teachers as Learners</strong></p><p>The HSBC Architecture team likes to seek feedback, even (or especially) when it tells us where we need to improve.</p><p>This year, our feedback told us that we needed to get better at communicating complex ideas in simple terms, and inspiring those around us to follow our ideas. That’s pretty important feedback for a team that’s supposed to lead the technical thinking of the organisation, so we decided to do something about it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S26UQmh9K--E773lo0CeGQ.png" /></figure><p>One of the things we did was to enrol in a course from HSBC University, called ‘Leaders as Teachers’. We didn’t really know what to expect from the course, other than it was highly recommended by the University faculty, and that it had something to do with communication.</p><p>Two days of very intense practical training and coaching later, we had acquired, tested and practiced important skills in facilitation. We’ve been using and practicing them ever since: hopefully our next round of feedback will show that we have improved.</p><p>We also learnt an important new concept, implicit in the title of the course: ‘Leaders as Teachers’. We had never really thought of ourselves as teachers before, but we soon realised that we spend a lot of our time teaching: coaching teams in new technology, in design and decision making skills and in how to solve problems. We also recognised something we had known all along: that teaching (educating, communicating, evangelising and otherwise equipping people with the insight to do the right things), is a far more effective way of getting our job done than governing (running committees, enforcing standards and approving or rejecting designs, and otherwise stopping people from doing the wrong thing).</p><p>I thought that might be a powerful enough lesson about teaching and leading for one year, but I had one more lesson to come.</p><p><strong>The Best Way to Learn is to Teach</strong></p><p>One of the speakers at our recent Engineering Summit shared the fascinating story of his career, and how he had developed both his technical and leadership skills. Among the tale of progress from starting out as a data centre operator to a senior leadership role, he offered the insight that <em>the best way to learn is to teach.</em></p><p>I had never thought about it that way before. Surely, the people who teach are the people who already know the subject. Yet, when I reflected, I realised that this was true.</p><p>I can remember one specific time in my consulting career, when my employer formed a partnership with a software company. I attended a training course to learn their product, but, as I was busy with lots of other work, and there was no prospect of an assignment using the product any time soon, I didn’t pay enough attention, and I didn’t learn much.</p><p>This turned out to be a mistake, as, a few weeks later, I found myself on a plane to South Africa, where I was scheduled not just to lead a project to deploy the product, but to teach the client how to run it themselves. You can believe that, in preparing for the start of that project, I learnt the product inside out and, fortunately, the project was successful.</p><p><strong>Teaching Helps Thinking</strong></p><p>And we can take this idea even further. Sometimes, by teaching, we are not just learning a new technical skill, but are learning exactly what our own ideas mean. When we have to teach those ideas to other people, we must express them with a clarity and confidence which tests our own thinking.</p><p>I’ve learnt some valuable lessons about learning and teaching this year. That’s why, when we recently launched our new HSBC Technology Academy, we made sure that we created lots of opportunities for our people to teach our people. That’s partly because many of our people have deep expertise which they want to share, but also because, for many, teaching is the best chance for learning they will ever have.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1f583bf2580e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Anti-Shunya for Careers]]></title>
            <link>https://medium.com/@dkoysta/anti-shunya-for-careers-e8aeba834d14?source=rss-4555b5c11075------2</link>
            <guid isPermaLink="false">https://medium.com/p/e8aeba834d14</guid>
            <category><![CDATA[banking-technology]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hsbc]]></category>
            <dc:creator><![CDATA[David Knott]]></dc:creator>
            <pubDate>Thu, 27 Sep 2018 11:15:33 GMT</pubDate>
            <atom:updated>2018-09-27T11:15:33.804Z</atom:updated>
            <content:encoded><![CDATA[<p>I knew that the concept of zero (at least as a positional notation) was invented in India, but I didn’t learn the Sanskrit term for zero (Shunya) until last month. My friend and colleague Balasubramanian Ganesh (HSBC’s CIO for Retail Banking and Wealth Management) introduced me to this term, and explained how we are using this concept (and a load of cool instrumentation) to drive zero defects, zero incidents and zero vulnerabilities for software engineering.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*av2GfEyATqMpiPI1Dy9Cgg.jpeg" /><figcaption>Ganesh explains Shunya at HSBC’s Engineering Summit in Pune, India</figcaption></figure><p>Ganesh also asked me on stage at our Engineering Summit in Pune, India, to share some reflections on my career, and to offer advice on what has helped me reach my current position of Chief Architect for HSBC.</p><p>My reflection was that, while Shunya is a great goal for software, it’s not something I have followed in career terms: my career has been full of defects, incidents and vulnerabilities. That’s because it has taken a while to figure out what I am good at, and it turns out that, to figure out what you’re good at, you have to do some things that you’re not good at.</p><p>Let me give you an example from the very beginning of my career: after finishing school, my original plan was to become a biologist. I was going to get my degree, and then pursue a career probing the secrets of life.</p><p>However, I had no idea what it was like to be a professional scientist. So, before starting university, I took a year off and got a job in a government lab, testing samples of fish for levels of pesticides. And I discovered that I was terrible at it: I didn’t have the patience and discipline for the precise, repetitive nature of lab work. It’s possible that I was the world’s worst lab assistant (and I am very sorry for the strange results in one of the batches, that had less to do with a spike in pesticide use than it had to do with me forgetting to add the solvent to the samples).</p><p>I also happened to get a job during that time as a programmer, and discovered that the programming skills I had learnt as a hobby transferred well to the workplace, that it was something I was good at, and that it was something I enjoyed. So I became a programmer.</p><p>If my career has a pattern (and I never set out to give my career a pattern), it is a repetition of trial and error. I have tried out lots of new things: I have been a programmer, an analyst, a DBA, a project manager, a programme manager, a CIO, a CTO, a consultant, and the manager of a business, as well as whole bunch of roles with loosely defined parameters and vague job titles.</p><p>I haven’t been good at all of them: in fact, I have found several at which I was very bad. However, each new role has helped me figure out what I am best at (roughly: explaining complex ideas in simple terms; building teams of people smarter than me; and getting those teams to solve difficult problems) and what I need to keep working on to get better.</p><p>I’m grateful to Ganesh for asking me the question at the Engineering Summit, because it made me reflect on the shape of a career that didn’t seem to have a very clear shape, and the value of taking risks by doing things that I don’t know how to do.</p><p>I’m hoping to go on trying new things, failing at some of them, succeeding at some of them, and to keep on discovering what I am good at.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e8aeba834d14" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>