<?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 Kris Zanuldin on Medium]]></title>
        <description><![CDATA[Stories by Kris Zanuldin on Medium]]></description>
        <link>https://medium.com/@kzanul?source=rss-3cb3e898dabe------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*a1ZqJiVW4GxuZXPc.jpeg</url>
            <title>Stories by Kris Zanuldin on Medium</title>
            <link>https://medium.com/@kzanul?source=rss-3cb3e898dabe------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 05:33:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@kzanul/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[Disrupting Toronto. For Real.]]></title>
            <link>https://medium.com/@kzanul/disrupting-toronto-literally-bbc7bea00a43?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbc7bea00a43</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Fri, 03 Jul 2015 01:12:13 GMT</pubDate>
            <atom:updated>2015-07-03T02:10:02.585Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Let’s apply the benefits of disruption to something that affects everyone’s everyday life: their city.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/540/0*edpe-lhZtjnNXNuS.jpg" /></figure><p>William Chan recently <a href="https://insouciant.org/tech/back-to-sf-after-usds/">wrote up</a> his thoughts of coming back to spend time at his employer, Google, after a stint in the US Digital Services. While he wrote of a sense of comfort coming back to all the perks of the Googleplex and hanging out with like-minded individuals working on new tech, the question that seemed to really be in the back of his mind was whether any of this was really important.</p><p>I have to admit I think about these kind of things once in a while and while I’m not going to go all Chris McCandless and give it all up, I do think it’s important for all of us to think about the work we do especially in tech which has such a transformative impact on society and people’s actual wellbeing. It’s quite hard to believe but the first iPhone was launched only eight years ago. Since then, the app economy has birthed all sorts of transformative services and behaviors that weren’t previously thought possible or scalable. Imagine in just a span of eight years how much our lives have changed with technology. Now imagine if that type of impact was focused less on the use cases of the better off and more on the worst off.</p><p>That’s why I get excited when I hear about initiatives like Google’s Sidewalk Labs. While I don’t necessary think they’re going about it completely in the right way, I am fully behind their objective — to make life in the city better. I’ve lived in a lot of big cities; from London to New York and Toronto to Kuala Lumpur — I’ve seen the type of life that the well-off enjoy but I’ve also seen the struggles of the inner cities and the not so great parts. Change comes to these parts very slowly and my hometown of Toronto is no exception.</p><p>Life in a typical city like Toronto is death by a thousand cuts. The little bug bears of dealing with public services and transportation won’t kill you but they will certainly sap your soul over time and we all just put up with it because we’ve all accepted that change won’t be coming any time soon. A big reason is that the municipal government is a grinding slow bureaucracy that still operates like it has operated fifty years ago. The whole disruption that has swept the for-profit sector has completely missed the public sector by and large. While companies have had to adapt to survive or risk going out of business — the government at all levels has never had that type of survival impetus driving them reinvent themselves. Some cities like London have made admirable steps to make a change but a lot of it tends to be more PR led then true product led.</p><p>Usually when a municipal government announces a digital or tech initiative it’s more about the PR to show that they’re not completely sitting on their hands but it tends to be very superficial. A partnership fund or a few hackathon events tends to cover the majority of these announcements. In most cases it’s about stroking egos (both the cities and the stakeholders). When you develop a product, you always start with the customer not the ego. This means finding out the real problems and pain points and building a solution around that. It’s also about being small and nimble these days, not lumbering and slow. Imagine the things we can do with technologies at our disposal today. Imagine if the city operated like Amazon — small distributed teams all across the whole city with ownership of services and platforms pushed down to the individual teams and a strong devops environment that allowed for continuous deployments. Imagine if all those services and platforms were built from the ground up to connect with each other and authorized 3rd parties (with appropriate security controls).</p><p>Can you imagine the type of experiences a typical Torontonian would have in their average day, living in a city that had that kind of engine of development driving behind the scenes? I can and I get excited about the possibilities when I do. Which is why if Toronto ever gets behind something like this, I’ll be the first in line to pitch in.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbc7bea00a43" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Six Degrees of Revenue]]></title>
            <link>https://medium.com/@kzanul/six-degrees-of-revenue-f793049e41e4?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/f793049e41e4</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Tue, 30 Jun 2015 01:36:40 GMT</pubDate>
            <atom:updated>2015-07-07T03:56:42.741Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2Fvyr0ldESsuMI8%2Ftwitter%2Fiframe&amp;src_secure=1&amp;url=http%3A%2F%2Fgiphy.com%2Fgifs%2Fkevin-bacon-vyr0ldESsuMI8&amp;image=http%3A%2F%2Fmedia.giphy.com%2Fmedia%2Fvyr0ldESsuMI8%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="448" height="249" frameborder="0" scrolling="no"><a href="https://medium.com/media/4be2671aad27a872fc1c2b12679fd0c0/href">https://medium.com/media/4be2671aad27a872fc1c2b12679fd0c0/href</a></iframe><p>There are some things that you learn as you grow up that are just harsh painful truths. Santa Claus doesn’t really exist. Cats can’t talk. You actually have to pay for that house you live in.</p><p>In the working world, the harsh truth I’ve learned is that everybody, and I mean <em>everybody</em>, is responsible for driving revenue. No, this is not going to be yet another one of those how do we scale our startup posts. Nor is it going to be one of those growth vs. revenue posts where we debate how much cash startups should be burning. Actually, I think Fred Wilson recently wrote quite a <a href="http://avc.com/2015/06/profits-vs-growth/">nice article</a> about the latter.</p><p>In fact — I’m not even going to talk about startups because what I’m going to talk about happens more often than not way on the other side of the spectrum in large-corporation-land. To be more specific, those teams and functions that self-identify as “cost centers” and to be even more specific — me calling bullshit to the whole notion. There should never ever be a concept of a team or function that thinks or identifies itself as a pure cost center. Of course they never really call themselves that. They call themselves support, operations or capability teams but what they’re really essentially saying is they’re not responsible for driving direct revenue due to the nature of their work — so please don’t judge them against it.</p><p>This is where I call bullshit. If you work in a for-profit company, no matter what the size, you are responsible for driving revenue. Period. You may not do it directly but you should be well within the six degrees of separation in regards to revenue. Probably more like three degrees but I call it six degrees so I can use my Kevin Bacon gif. What bothers me is how quickly (and easily) the vast majority of teams and individuals wash their hands of this mindset which you can argue is the single biggest factor in a business’ ongoing viability — and by extension their own employment. This is a dangerous fallacy. The moment you think like this, no matter if you work on product development, operations or support functions without revenue as your primary motivator or performance goal, then you are essentially drifting. In good times, these warts can be concealed but when times are tough, this type of bloat is the first to go. I still have this stark image in my mind from when I worked for a previous employer where topline revenue was starting to flag a little. There was a big gathering offsite in my organization to help jumpstart the focus on driving topline revenue. You could literally see the thought bubbles in the room where almost everyone in the room was completely paralyzed with indifference because of the fact that they felt they had no real direct relationship to driving topline. I can imagine the next time the accountants take a good, long hard look at those type of orgs — they’ll have some thought bubbles of their own.</p><p>So even if it is just for the sake of self-preservation, if you are a corporate wage slave and consider yourself not in a position to drive revenue — let me give you a few suggestions:</p><p><strong>1. Think of it like playing pool</strong>: You may not have a direct link to driving revenue but in most cases you’re probably linked by one degree, maybe two from the direct drivers. What you need to do is identify what that linkage is and how you can manipulate it with the sphere of influence that you do control. It’s like trying to sink the eight-ball in the lower left pocket — you don’t hit it directly but you control everything with how you hit the cue ball to get the desired result. For example if you’re in support, map a DSI impact on revenue to customer contacts. You control how you manage customer contacts which in turn affects DSI and revenue. Similarly in product development. Your product features drives usage that should always be tied to revenue in some way (directly or indirectly).</p><p><strong>2. Map everything you do to those levers</strong>: Take a good long look at everything you and your team is working on. Everything on that list needs to map back to those “cue balls” in your control that affects revenue. Again, it can be one degree or two degrees removed but it needs to have a clear linkage. If it doesn’t — ditch it.</p><p><strong>3. Use goals as a litmus test and a motivator:</strong> To test the strength of a linkage — set some hard revenue numbers as goals for your team and yourself. Starting to sweat a little, huh? Good. Nothing removes the bullshit better than the Sword of Damocles hanging over your head on delivering results. This is a great litmus test on whether you are confident the things you work on will impact revenue. Again, if you’re not confident — ditch it.</p><p><strong>4. Reorganize yourself and your team and execute: </strong>You now have clarity of focus and (hopefully) a much better understanding of your revenue levers. With that, it now comes down to that tried and true factor: execution.</p><p>So there you have it. You’ll be amazed at how much extraneous stuff you cut out when you put yourself in the revenue mindset — no matter what your role or function. You’ll start to constantly question whether the things you’ve always been doing or expected to do is really helping drive the top line. You’ll be willing to push back more and think harder on what you should work on. Last but not least — you’ll probably still be employed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f793049e41e4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cheetahs in the Serengeti]]></title>
            <link>https://medium.com/@kzanul/cheetahs-in-the-serengeti-45b3ff7f1acd?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/45b3ff7f1acd</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Wed, 29 Apr 2015 06:28:54 GMT</pubDate>
            <atom:updated>2015-04-29T06:53:21.026Z</atom:updated>
            <content:encoded><![CDATA[<h4>Wading into the gender diversity discussion</h4><p>It’s been quite a busy month with a lot of heads down work but if there’s one thing that appears to still be sacrosanct — it’s the team Friday happy hour. I&#39;ve always looked forward to it because it’s a chance to unwind a little after a long week and just shoot the s*it with the team. It was at one such recent happy hour that I found myself unexpectedly drawn into a conversation with one of the female software engineers around the hot-button topic of gender diversity in tech. I won’t rehash the chatter around the issue as there’s plenty of it already in the mainstream. However, it really hit home for me when she was talking about her old job at Microsoft and how of the 80 engineers on the team, she was one of seven females. By the time she left Microsoft, there were a grand total of two left on the team.</p><p>In general I&#39;ve actually tried to keep my head above the whole gender diversity debate. Primarily because I&#39;ve always had a pretty simple view when it comes to hiring talent on the team. It’s hard enough finding individuals that are above the bar so as long as you&#39;ve got the right stuff and write good code — you can be a purple alien from Mars for all I care.</p><p>However, I realize this is pretty much a naive view. It’s easy to take the “I don’t care who you are” view and pat ourselves on the shoulder but we’re not really helping the issue in any way. In fact it’s the wrong way to look at it. We should look at it like cheetahs in the Serengeti. I&#39;ve always had a fondness for cheetahs. Perhaps it’s because unlike lions or tigers, they’re not trying to eat you. Or perhaps it’s an evolutionary appreciation of an animal that has evolved into a single minded specialist. So what the hell does cheetahs in the Serengeti have to do with gender diversity you ask? Well interestingly enough the average survival rate of a cheetah cub is around 10% in the Serengeti. Due to the harsh environment and the relative physical weakness of the cheetah, not many of them live to adulthood. On top of that, due to their specialized nature, when they hunt, they rely purely on their speed and nothing more. The average success rate for a cheetah when it hunts is around 50%. Add it all up and we’re talking about insane odds. So if you’re an adult cheetah that lived up to that point and actually manage to sustain yourself — YOU ARE VERY GOOD.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LvHvYRornMY4DKzBlQMINQ.jpeg" /></figure><p><em>Female software engineer candidate</em></p><p>Now think about it in that context on hiring female engineers. In the last three months as I was hiring engineers for my team, I can count on my fingers the number of female candidates I saw — just in the pipeline. Reduce that through the regular candidate filtering process and the brutal four and a half hour interview loop process and the odds that an inclined candidate shows up that would be a female are like cheetahs in the Serengti. So if a female candidate makes it to the final round, even though we would evaluate them next to all the other male candidates and pick “the best one”, I can tell you just getting to that point is something that is greatly under-appreciated for a female candidate and we all need to do a much better job of recognizing that.</p><p>However, just recognizing it or giving credit can help a little but it isn’t going to solve the underlying issue. To really fix this, we’re going to have to trace back to the point of origin and address it there.</p><p>That’s a post for another day but if you’re feeling like making a small difference, <a href="http://girlswhocode.com/donate-2/product-category/donate/">here’s</a> a suggestion. Or <a href="http://gifts.worldwildlife.org/gift-center/gifts/Species-Adoptions/Cheetah.aspx">here</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45b3ff7f1acd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Show Me.]]></title>
            <link>https://medium.com/@kzanul/show-me-8e9d3685a4ad?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e9d3685a4ad</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Sun, 08 Feb 2015 20:29:01 GMT</pubDate>
            <atom:updated>2015-02-10T13:34:11.089Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/968/1*IBmByw3EPG_hLB3ylJcVrQ.jpeg" /></figure><p>My favorite part of the agile process (other than shipping) is the sprint demos. These “show me” sessions are great because they reaffirm all the hard work the team has been doing for the last two weeks in a tangible form that you can see (as well as sometimes feel and touch).</p><p>I&#39;ve always wondered why these things need to be restricted to just product development. For example, I’ve incorporated it into the marketing activities for the team as well.</p><p>In parallel to our 2-week product dev sprints we run 4-week “marketing sprints” because well frankly, scaling anything new is a continuous marketing effort. You’re trying to prime the pump from a standing start so one-off campaigns won’t cut it.</p><p>We plan releases, identify blockers and manage the backlog and yes — we have “show me”. What I like about this is it creates a forcing mechanism and a sense of urgency. Unless you have a product launch or some big event, I&#39;ve found historically most marketers take a very <em>laissez faire </em>approach to their initiatives.</p><p>This has been typically my experience in marketing at a big company: someone creates a deck with a bunch of nice bullet points and boxes about all the stuff they’re going to do. They have a meeting. Out of these meetings — more meetings are scheduled. One or two of those bullet points start some initial work. More meetings and decks. Then one of the bullet points gets to the actual development stage. Cue more “update” meetings. Finally the campaign launches…3 months later. By the end of the year about 10% of those bullet points were ever actually launched and the remainder either gets swept away or recycled as more bullet points for next year’s deck.</p><p>Sound familiar?</p><p>This is a ridiculously inefficient approach to marketing when you think of the competitive environment we work in nowadays. Now I have some issues with agile (I stripped out half the Scrum process bullshit because it’s just that) but I think marketing could benefit from some form of XP. Think of it as XM — Extreme Marketing.</p><p>Ditch the decks. Organize and prioritize your backlog with a starting range on team capacity. I find four week sprints work well for me because there are some realities around launching marketing initiatives which I accept but play around and figure out what works for you.</p><p>Then comes the real change: actually work through your sprints, discuss your blockers at standups and ultimately have your “show me”. If your team can’t produce something by the end of the sprint — you have to fix it and fix the team. Freedom and responsibility comes with a healthy dose of accountability after all.</p><p>There’s no hard and fast rules around all this — it’s ultimately about creating forcing mechanisms. One of my favorite Jeff Bezos quotes is: “Good intentions never work, you need good mechanisms to make anything happen.” For those that know me you know I also do not believe mechanisms equals process, so make sure you don’t start over-indexing on that side either!</p><p>It may take a while but once your team finds its cadence you’ll be amazed at how much progress you can make.</p><p>Or you can go back to drawing more boxes and bullet points. Your choice.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8e9d3685a4ad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Freedom and Responsibility]]></title>
            <link>https://medium.com/@kzanul/freedom-and-responsibility-43f5de43c241?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/43f5de43c241</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Tue, 02 Dec 2014 08:05:44 GMT</pubDate>
            <atom:updated>2014-12-02T22:55:04.274Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/630/1*RSQ1Dz4SsKqB8-uee7A9IQ.jpeg" /></figure><p><em>Five years on and I still feel this is one of the best culture presentations out there</em></p><p>There’s a lot of crud out there when it comes to advice on how to manage and grow a truly innovative team. At any time of day, a random scroll through my Twitter and LinkedIn feeds will uncover yet another cringe worthy article on “how to be innovative”. It almost makes me wonder if there really are people out there that believe some of this stuff or we’re all just the subject of bot-driven content farms churning out these click-bait articles.</p><p>If you haven’t noticed by now, I’m a bit of a cynic when it comes to these things. Chalk it up to more than a few experiences, in more than a few companies, in more than a few cities. However, for all the muck out there, there are some really good diamonds. The simplest approaches tend to be the most effective. One of the seminal pieces of innovation culture that I still refer to is Reed Hastings’ famous “<a href="http://www.slideshare.net/reed2001/culture-1798664">Freedom &amp; Responsibility</a>” presentation on Netflix culture. It’s more than five years old now but that just goes to show how effective a perspective I believe it to be. I made it recommended reading for any potential prospect that was interviewing on my team and mandatory reading for anyone who joined it. Why? Because I believe the basic tenets of Freedom &amp; Responsibility as elaborated in Reed’s presentation (and executed at Netflix) is fundamentally what works. It doesn&#39;t mean you have to execute it exactly the way Netflix does but the core is absolutely spot on.</p><p>There are two major concepts that I have taken in wholeheartedly. The first is around values. It basically centers around this: talk is cheap on saying your values are all those words on those iconic motivational posters you see in every office. Real values are behaviors you want your employees to exhibit and employees tend to exhibit behaviors that they are financially motivated to exhibit. i.e. you pay Jim to jump left — he’ll jump left. Values are the behaviors a company rewards through promotions and pay. People who exhibit the right values get promoted (and paay-ed). It’s almost Pavlovian in its simplicity but it’s true. Truth, integrity, the American way. They’re all just words on paper. Real values are what gets you promoted or paid (or both). So why is it people are so surprised to find companies who describe themselves as “innovative” or “entrepreneurial” in their value statements are usually the ones that are the most resistant to change, suffer through corporate inertia and lack of creativity? It’s because the people they promoted are like that. So the first piece is — if you want the right mindset, then pay those behaviors that exhibit those mindsets. Simple right? But it’s rarely done. It’s because most companies don’t really want those mindsets. They say they do but when you dig down to who they promote and pay, they really want other things more. Steady hands at the till, risk mitigation, operational excellence. Those are the behaviors more often than not that get promoted or rewarded because those are the company’s true values. So if you’re looking to join an organization that’s truly innovative or are trying to create one — just look to who and how they promote.</p><p>The second major part of Reed’s presentation that I have taken to heart is the concept of Freedom and Responsibility. I believe in this so much I’m sure I’ll get those two words inked at some point. When you’re a small outfit, you have a ton of freedom but with that freedom comes the responsibility to deliver, because so much is dependent on you. There’s not alot of safety net out there. In most cases, the companies that make it are the ones with the rockstars that can handle this chaos and manage it. As the team and organization grows with success, the complexity of the business grows. Soon it grows too much for the rockstars to handle by themselves. More people get brought in but they’re not rockstars. They’re headcount fillers. Talent gets diluted and complexity overtakes talent. Too many mistakes get made. At this stage the only logical step to bring about order is to introduce process. Process — the anathema of innovation. The order process brings is addictive. It seems great because even the non-rockstars benefit from the process. They’re good at process. It takes away the chaos but like a great painkiller it also numbs the good stuff with a nasty side effect. The creativity and innovation that made the team great in the first place is lost. All is not lost as Netflix argues there’s another way. Instead of introducing more process, just introduce more rockstars. Instead of having complexity overtake talent, keep talent ahead of complexity. They believe this model can work and this model can scale. Their approach to doing that is to pay maximum market to the rockstars and ruthlessly eliminate the ones that aren’t rockstars (or ex-rockstars because blind loyalty is also identified as ineffective).</p><p>Now all this is easier said than done. Even Netflix can’t completely avoid non-rockstars (or process) but the point is if you do it enough it’ll make a difference. I’ve seen it make a difference which is why I believe in this. Even if you’re just a piddling middle-manager with limited power and influence? Yes even if you’re just a piddling middle-manager Walter. It’s true for the real benefits of Freedom and Responsibility to manifest, the whole company has to change — especially around HR policies and compensation. But that doesn’t mean you can’t start practicing it on your own team. Take a look at your talent. Ruthlessly ask yourself who you’d absolutely fight to keep from leaving. Exert your maximum influence to pay them maximum and start to exit the rest. The non-rockstars may be great at process but they’re dragging down your team’s independence. Advocate for the ones that exhibit the real behaviors you want.</p><p>Then — and this is important — step back and give your own team freedom and responsibility. It still amazes me how many people so desperately yearn to be given maximum leeway to be creative, yet turn around and micromanage their own team. If you have the right talent on your team, you shouldn’t need to micromanage. It’s simple and it’s true. Micromanaging just means you have non-rockstar talent or you’re just an ass of a manager. One or both.</p><p>Team independence is great for you because it means you can focus on being an actual manager — hiring more rockstars, reinforcing the right values and just pushing that talent flywheel round and round. You may not be able to make a whole company an innovation-machine, but damned if you can’t make your own team one.</p><p>Freedom and responsibility. It’s as simple as that.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=43f5de43c241" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[In Meetings, Parkinson’s Law Prevails]]></title>
            <link>https://medium.com/@kzanul/in-meetings-parkinsons-law-prevails-5685518c9ead?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/5685518c9ead</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Sun, 13 Apr 2014 01:02:42 GMT</pubDate>
            <atom:updated>2014-04-13T01:02:42.650Z</atom:updated>
            <content:encoded><![CDATA[<h4>Time to cut down on meetings. Seriously.</h4><p>As my team will tell you, I’m notorious for wanting short meetings. In fact, the shorter the better.</p><p>The reason for this is that I’ve found that meetings tend to adhere to a form of <a href="https://en.wikipedia.org/wiki/Parkinson%27s_law">Parkinson’s Law</a>: meetings will fill up the time allocated to them. Hence if you schedule an hour long meeting, you’ll end up taking the whole hour — regardless of whether you could have achieved the objective of the meeting in less.</p><p>Meetings should be viewed as a necessary evil because for every minute you take up “meeting” you could actually be <em>doing </em>whatever you were meeting about in the first place.</p><p>Now I agree — there are times when you do need to meet. When you need to decide, inform or solve. To solve a problem, you need to get together and collectively crack on it. I get that.</p><p>However, in all those cases, if there’s one thing I can’t stand, it’s <em>meetings without a point</em>. I’m not talking “agenda” point. I’m talking real point. The worst are the “let’s touch base” ones that don’t have a really clearly defined objective (even worse if one or both of the parties tend to be more introverted). Every meeting, no exception, should be biased for action which means that everyone recognizes the only reason they’re taking time out is because there’s something really important that needs to be done that couldn’t be done without coming together collectively. Any meeting that can’t meet (no pun intended) that objective should not have happened in the first place.</p><p>Once you do decide that meeting is necessary, then everyone should do their utmost to achieve their desired outcomes in the shortest time possible. Think of it as accelerated depreciation. There’s less value the longer it runs.</p><p>People love to sandbag their meeting times which just risks them falling into Parkinson’s law. My advice: worry less about the time you have in a meeting and worry more about how you’re going to get what you need done.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5685518c9ead" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Let’s Replace Don’t Be Afraid To Fail With Survive At All Costs]]></title>
            <link>https://medium.com/i-m-h-o/lets-replace-dont-be-afraid-to-fail-with-survive-at-all-costs-a6756611f30e?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6756611f30e</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Mon, 16 Sep 2013 15:38:53 GMT</pubDate>
            <atom:updated>2013-09-16T15:38:53.442Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*iEG6dW1q4r_Z8GVg.jpeg" /><figcaption>CBS/FOX: DIE HARD</figcaption></figure><h4>No, it’s not okay to fail.</h4><p>It starts out at a high level as a good idea, but just like best intentions, somewhere along the way it’s gets warped to hell.</p><p>I’m speaking specifically about the whole phrase, “don’t be afraid to fail”. It’s definitely a phrase that gets cited widely as one of the necessary ingredients in startup success but has made its way into the general mainstream. For any project, initiative or just about anything you do — you should not be afraid to fail.</p><p>On one hand, I do agree with this in the sense that it encourages boldness — which I like. On the other hand, I think the unwanted side-effect is that it also encourages a false safety net, that this notion of failing is okay — which I abhor. Removing the stigma of failure is okay, but not to the point of encouraging needless stupidity due to a false sense of security that no matter what happens — you’re still a winner.</p><p>It reminds me of an old King of the Hill episode where Hank gets involved with Bobby’s soccer team. At one point, Hank is incredulous when the coach whistles, “Tie-game! Everyone’s a winner!” just to make everyone feel good.</p><p>Nobody should fail. You should avoid failure at all cost. It’s painful, time-consuming and costly. The key thing is how you approach this failure-avoidance. Are you going to cower away in the corner, avoid all risk and be the <a href="http://en.wikipedia.org/wiki/The_Bubble_Boy_(Seinfeld)">bubble boy</a> or are you going to avoid failure by being John fucking McClane and survive at all cost.</p><p>Somewhere along the line, the researchers and quants that analyzed the success stories of startups past have all pointed to the fact that the ultimately successful entrepreneurs are the ones that weren’t afraid to fail. Actually, from what I’ve seen, the ultimately successful entrepreneurs were the bloody cockroaches that refused to die no matter what setbacks they encountered. Failure had nothing to do with it. It wasn’t the fact that they approached their businesses with the idea that it was okay if they failed, it was the fact that they approached their businesses with the idea that they were going to outhustle, outsmart, and outwork everyone out there to make sure they lived to fight another day. That is what strikes me as a more common factor to success than a quaint notion that they had a mindset of “failure is ok”.</p><p>You might argue that I’m splitting hairs but there really is a big mindset difference between those that go about their business thinking, “well no matter what, it’s okay to fail and I got the learnings” to those that think, “I will survive at all costs and be resilient no matter what”.</p><p>So the next time you hear someone tell you, “don’t be afraid to fail”, politely correct him or her and say, “actually I don’t intend to fail because I intend to survive at all cost.”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6756611f30e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/i-m-h-o/lets-replace-dont-be-afraid-to-fail-with-survive-at-all-costs-a6756611f30e">Let’s Replace Don’t Be Afraid To Fail With Survive At All Costs</a> was originally published in <a href="https://medium.com/i-m-h-o">I. M. H. O.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Premeditation in the User Experience]]></title>
            <link>https://medium.com/@kzanul/premeditation-in-the-user-experience-f8ea840cdea5?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8ea840cdea5</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Tue, 16 Jul 2013 21:05:29 GMT</pubDate>
            <atom:updated>2013-07-16T21:05:29.621Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ntpo_Yf5PR14MB2Z.jpeg" /></figure><p>Today I tested out one of my team’s new builds for a prototype. I got in my car and drove to a local business to use it in a real life scenario because frankly, some of the best feedback you’ll ever get is your own experience in a live environment (and if something’s not right - you’ll know).</p><p>One thing I immediately noticed is that the user experience of said product was well thought out but really when put in the context of the real world, there was a significant amount of premeditation required. What I mean by this is that the customer really has to be in the frame of mind and have the product top of mind when in a situation where they would use the product. This is something that rarely happens as these “moments of truth” are split second and people naturally fall back on habitual behaviours. The likelihood they’ll use your product now is very low unless you’re really bringing something big to the table that will overwrite that habitual behaviour. This is something product owners and developers tend to really lose sight of and forget when designing products and experiences.</p><p>While the UX may be slick, it means nothing if you can’t really capitalize on the split second decisions that happen when customers are faced with scenarios where they <em>could </em>be using your product. You need to make sure your product minimizes premeditation.</p><p>Take Google maps for example. Brilliant product and great UI that I love and use regularly, but does nothing for me when I’m desperate to find out whether the upcoming exit on the highway I’m driving on is the right one. Still requires some level of premeditation and I would argue that Google maps is actually a good example as map reading tends to be a premeditated activity in general. There are plenty of apps and solutions out there that have a huge reliance on premeditation for situations that really are more typically “spur of the moment” and hence is one of the reasons why alot of them never gain traction.</p><p>Going back to the team, I think one of the things we’ll have to focus on is how to reduce premeditation whether by appending another experience/function that will more naturally segueway to the core product (if I’m already using my phone for X then using it for Y tends to be less premeditated since I’m already in the experience) or alternatively re-do the experience completely. Never a fun thing to do but much preferred than being stuck with a product over-reliant on premeditation for success.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8ea840cdea5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tasting The Rainbow]]></title>
            <link>https://medium.com/@kzanul/tasting-the-rainbow-7164083cfc8f?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/7164083cfc8f</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Fri, 05 Jul 2013 18:05:57 GMT</pubDate>
            <atom:updated>2013-07-06T01:17:03.550Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/699/0*vsbshiBe_AIQNb1U.jpeg" /></figure><h4>It’s time I started giving other colors a fair shake</h4><p>My father in-law just bought a new car. The one part about it I think he was a little surprised in was the color. The brochure had it as a nice traditional, conservative blue and it came into the lot in a much louder, candy-like blue.</p><p>Opinions in the family were mixed; the general feeling was that it was <em>weird. </em>It definitely stood out among all the other cars in a parking lot or on the road. I personally thought, “Glad I’m not driving that. I’d feel self-conscious”.</p><p>However, circumstances found me driving the car for the past month (the in-laws were on vacation so I borrowed theirs as my wife and I are still sharing a car since our move back from London).</p><p>In that time, I’ve grown quite attached to the color. I like how it stands out, how it’s different but in a nice way. Someone at the Toyota design department wasn’t that crazy after all. It’s also made me realize that I’m quite conservative in my color life. From clothes to decks and websites, I’ve always played it conservative - keeping it simple and never straying too far from the safe arms of black, white and blue. Look in my closet and my business shirts pretty much follow that palette. This color conservatism has seeped into ever part of my life. My phone is black. My bag is black. My iPod is white. My jeans are blue.</p><p>Superficial as it may sound, I’ve become quite concerned over this. For some reason or another, I’ve singled out an upcoming presentation for later this month to finally do something about it. Partly since it was a personal presentation I could go a little wild and not worry too much about the corporate brand hounds coming after me and partly because a presentation seemed like a good place as any to explore new color vistas.</p><p>I’ll have to be honest, it was quite a daunting exercise to consciously stray away from any of the traditional colors and ranges I would normally rely on (a ground rule I set for myself). Everything felt weird and uncomfortable. Good. It seems I was on the right path.</p><p>I also wanted to still do a good job and wasn’t sure I would be able to credibly pull off something like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/370/0*6pylPFs0KgXZoT-v.gif" /></figure><p>My colors had to at least have good harmony - even if they weren’t my traditional choice. Fortunately, I found an AMAZING tool that took care of that. <a href="https://kuler.adobe.com/">Adobe Kuler</a> lets you create complementary color wheels and swatches and even see what other great designers have come up with. It makes it hard to really go wrong with your color choices.</p><p>I’m pleased with where I’ve ended up and my mini-excursion to the other side of the rainbow. More trips definitely in store for the future. As for the presentation, I’ll post it up on Slideshare and update this link after I present later this month and you can be the judge.</p><p>Perhaps I’ll even try and slip one by those corporate brand hounds.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7164083cfc8f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Death By (To) Powerpoint]]></title>
            <link>https://medium.com/i-m-h-o/death-by-to-powerpoint-4741d11ece60?source=rss-3cb3e898dabe------2</link>
            <guid isPermaLink="false">https://medium.com/p/4741d11ece60</guid>
            <dc:creator><![CDATA[Kris Zanuldin]]></dc:creator>
            <pubDate>Thu, 27 Jun 2013 15:44:14 GMT</pubDate>
            <atom:updated>2013-06-27T15:44:14.527Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GKy_EnpWK6TaeaRa.png" /></figure><h4>Let’s get back to story telling (but if you have too…)</h4><p>Work in the business world long enough and you won’t escape one inevitable fact – you will need to do a deck.</p><p>Deck writing has become a job in itself for me and if you follow <a href="http://www.youtube.com/watch?v=XS5EsTc_-2Q">Malcolm Gladwell’s theory</a>, I’ve definitely logged my 10,000 hours… and then some. The issue that I have with decks is that it’s been taken too far in the mainstream. The medium has indeed become the message. People are now way too focused on the decks that they’re spending their time consumed with talking about what they’re doing instead of exactly that: <strong>doing.</strong></p><p>There are plenty of days where I’ll walk past desks and all you’ll ever see up on the screen is powerpoint. It’s become the grease that runs the daily cogs of Corporate (insert country) and that is not a good thing.</p><p>However – if you’re going to do a deck, at least do it right.</p><p>I’m not opposed to decks. I actually enjoy a good presentation where the presenter uses the software for it’s actual original purpose to help engage and tell their story whether in person or virtually. People are visual creatures and respond to well designed cues to better follow and remember the story being told. However people have now bastardized the medium where powerpoint slides now serve the purpose of an analytical data dumping ground, walls of text or the worst possible sin – a replacement for the presenter themselves.</p><p>I’d like to suggest we get back to our roots and use presentation software for its intended use: <strong>story telling</strong>. Everyone is trying to just tell a story – no matter if it’s what revenue growth has looked like in the past four quarters to demo’ing the latest hack – it’s just a story at the end of the day.</p><p>So here are my simple rules that I like to keep in mind when dealing with a presentation:</p><p><strong>#1: Never follow a presentation rule off a cliff (including mine). </strong>There are so many articles out there around how to be a better presenter. What the do’s and dont’s of presenting are, blah blah blah. The problem I have is first of all – there are no golden rules in presentations. That’s what makes it great -it’s a creative exercise that works better when it can be interpreted – and delivered in different ways. I also have an issue with alot of the advice that treats everybody like they’re the same. As if everyone liked their steak the same way (medium rare for me thanks). <a href="http://makeapowerfulpoint.com/2012/03/09/the-6-presenter-types-which-one-are-you-2/">People are different</a> and have different styles. Trying to change your style to fit a version of what’s the “right way” is a recipe for disaster. Often a lot of people ask me for tips on presenting and how to adopt my style and my advice is to not try so hard to adopt someone else’s style. Pick out the elements you like and fit your own personality and you’ll go miles further than trying to fully replicate someone else.</p><p><strong>#2: Focus on you. </strong>People like to hear great story tellers and not their presentations. There’s a big difference. The presentation is a cue, a background to the main attraction - you. If you’re relying on your presentation to tell your story - then you’re eliminating yourself. Don’t reduce yourself to the equivalent of a human clicker. If you want your information to be read - use other mediums like … well Medium. Use your decks for helping the focus remain squarely on you and what you’re saying.</p><p><strong>#3 Sex sells. Period. </strong>As I said earlier – people are visual creatures. They like to respond to nice design, good user experience and pretty things. The purpose of your presentation is to keep them engaged in your story. Putting dry text and bullet points gets the point across but is it really keeping them engaged or are they fighting back yawns to keep paying attention? Now this does not mean that you have to make all your presentations a flashy, all-singing, all dancing beast or a fluffy showpiece. It just means inject creativity into each of your slides with some elements that will keep your audience paying attention, which brings me to my next point…</p><p><strong>#4 Simple is good. Simple is hard. </strong>You don’t need to be a kick-ass designer to do a nice creative deck. It doesn’t hurt but I’ve seen equally effective and engaging decks with just the creative use of fonts, backgrounds and complementary color palettes. Just like a stage actor can keep an audience as engaged as a multi-million dollar feature film – simple can actually go a long way. One of the worst mistakes I see is that people take rule #2 to heart and start saturating their decks with copy and pastes of the latest clip art and random stock images they get off Google Images. No, no, no! Use your images sparingly, with good quality (please ignore the temptation to stretch those images thank you very much) and always with a specific purpose of helping your narrative not because it looks cool.</p><p><strong>(Bonus) #5 Everytime you micro-manage someone’s presentation, a kitten cries. </strong>This is for all you managers out there that love to give back your direct reports’ decks back with a gazillion markups. Remember rule #1. They are not you. Don’t try to enforce your style on them. It kills their engagement and is actually hurting their long term development. Sure – I’ve seen plenty of presentations from people that make me cringe but here’s the thing – unless I intend to deliver the presentation – it’s not my deck and I should not act like it is. And frankly, if it was your deck – why the hell are they doing it and not you? L-A-Z-Y. That’s not to say you can’t help. You can give suggestions, you can deliver high level commentary and examples, but never micro-manage. Of course you want your reports to look good and there’s always a minimum level of quality that you want to enforce but micro-managing is a lazy man’s way to getting there. Everyone needs to find their style and the best thing you could do for them as a leader is help them find their style and give them opportunities to practice.</p><p>The reality is we need to cut back on our powerpoint in general and utilize other mediums such as white board discussions or hands-on conversations that encourage more of a bias for action than powerpoint presentations do (my theory is that powerpoint actually encourages inertia by keeping people so busy writing decks).</p><p>So the next time you’re faced with a deck the first step is to ask yourself if you really need one.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4741d11ece60" width="1" height="1" alt=""><hr><p><a href="https://medium.com/i-m-h-o/death-by-to-powerpoint-4741d11ece60">Death By (To) Powerpoint</a> was originally published in <a href="https://medium.com/i-m-h-o">I. M. H. O.</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>