I saw this today on the HBR Daily Stat – Narcissistic CEOs Take Bold Action When There's an Appreciative Audience. Very insightful and, sadly, often a driver for change in things that may not yet be broken – or just changes to make changes. Definitely worth a read. I can see how it could impact a project – especially with Agile. A sudden reprioritization or change to satisfy an ego rather than a bottom line. Or stories are written to support the disruption rather than see how the disruption can contribute to the company. Something worth thinking about….
Month: July 2013
Going to add some video blog entries…
Stay tuned – I'm going to try to make this a little spicier and add some clips of me talking instead of my treatises or rants. I hope you enjoy!
Friday Rant – making a vendor responsible for your strategy
Project roles. We don't talk about them enough. Each team member contributes something different to a project, which is why we need a team. Sometimes we augment a team with vendors – especially when we need temporary help in an area. But what happens when you "outsource" your strategy?
Yes, you heard me. Outsource your strategy.
This is baffling because I wonder why someone would be an employee if he is outsourcing his company's strategy and basically, the business he works for? This mentality is great for slippery personalities who use this strategy to get promotions (and proclaim "Look at what I did," when in fact, a vendor did it) or to avoid being fired ("That crazy vendor did that!"). However, when you own the numbers – from metrics to revenue targets, know the inside details about the future vision of the company, understand your client needs and the relationship dynamics with them, understand your internal culture and politics, and a number of other decision making factors – HOW CAN YOU NOT OWN YOUR OWN STRATEGY?
But taking this one step further – why would a vendor take on a strategy project, where the vendor owns those decisions, without having access to this information and assume the risk of flying blind to run someone's business? And I have to ask the question – even if a vendor got this information, why not just convert to the "dark side" and be an employee?
Role of a vendor: The vendor is providing additional thinking to help the employee see different options. Sometimes an employee is so into the company "box" that he doesn't see it. It happens. And you need to hire someone to think outside of that box. You give that consultant numbers and data to be creative, and you pay for some new ideas.
Role of the employee: Give the consultant the data he needs and then make the final decision as to what will be successful.
When you ask the consultant to provide a strategy (hidden in a request to recommend options without the consultant knowing all of the facts), you are reducing your risk to almost zero but putting the consultant at GREAT risk because there is no way for a consultant to make 100% informed decisions or recommendations without knowing all of the internal factors. And if you keep putting a consultant at risk, your consultant will stop being your adviser.
This is something I see time and time again – and I don't fully blame the employee trying to get away with it; I also blame the consultant to accepts this type of work and doesn't set that boundary of where decision making lies. The roles and responsibilities for a project need to be clear up front. I know I have been in situations as a quasi-employee. However, when it came down to making a final decision for a direction – I stayed out of it. I just made sure the employee I was working with thought through all of the various perspectives for all solutions when he or she made the decision. At the end of the day – it really wasn't my decision(s) to make.
Ok…I'm off my soapbox now. Have a great Friday!
Improv and Agile/UX: Part 1 – Being Prepared
On the side, I am a Classic Egyptian belly dancer. I know – it's not something you would expect to read on a blog about UX and Agile; however, it is something that has affected me deeply and has dramatically changed how I view work and life. Some people view belly dance as derivative of stripping – it is far from it. There are countless articles about its history as an art form and its uniqueness in that no Egyptian belly dance performance – even if loosely choreographed – is ever the same twice. It's about expressing emotion of the moment and that always brings up some nuances here and there. I know – a stark contrast to Agile and UX at first glance. However, if you dig deeper – it's not all that different – especially when it comes to creating experiences and working with others.
As something different, I decided to write a series about what I learned from improv Egyptian belly dance and how it influenced me to become a better Agile/UX practitioner. This is the first part, which is focused on self-confidence and being prepared.
Doing improvisational Egyptian belly dance has taught me a lot about life. Generally, to successfully perform improv (meaning, the audience can make sense of what you are doing onstage) your mind has to be very flexible and highly responsive. Over time, you learn how to think fast on your feet and respond immediately to anything that's thrown your way.
A lot of people ask me, "isn't it stressful to dance to live music?" When I first did it, yes. I was in a panic before every performance, hoping I'd get a song I could dance to and do a good job (rather, I could perform a choreography). As time went on and I learned how to work with live music, it got much easier. And I realized the key was to rely less and less on choreographies (planning) and more on being prepared.
Planning and having a stash of too many contingency plans doesn't make you prepared – it's just too much to remember and too complicated to keep all paths in the front of your mind. So what do I mean by being prepared?
Being prepared is self-confidence
- You know that will do the right thing at the right time based on what you know about the music (history, lyrics, melody, etc.)
- Your are comfortable with expressing your emotions in front of other people
- You know Egyptian music so well that you have an idea of what the band will do before they do it – strong intuition
- You are ok with being present, in the moment and dancing in the now rather than thinking about what's 5 steps ahead or worry about what the band will do next
- Being open to the unexpected
- Open to learning – experiencing success and failures
- Different definitions and values of success – the audience is pleased, self-fulfillment, fluid performance
- Open to the ideas of others (typical for Egyptian improv – the band may play a song you aren't familiar with or don't expect – but the show must go on; or what you think is great – the audience doesn't care for and you need to adjust – quick!)
Basically, being prepared is having the ability to respond to what is thrown your way without hesitation (unless you feel that hesitation is needed).
Having a plan is confidence in your plan
- You hope that the band plays a song that goes with the choreographies you know
- Value performing steps/footwork over interpretation. You want to be technically perfect and perform each step perfectly rather than express emotion.
- Plans are like a software program – if/then statement. They are not fluid by nature and don't explore possibilities or going down a new path
- You, the band, and the audience are separate groups – not a single organic organism that all contributes to the experience
The plan, choreography, is everything. If the music deviates from what you know – you are helpless. It's about the math of the dance – counting, hearing beats. It's not about feeling the music and feels right to come next.
In so many ways, what I learned from Egyptian dance, being prepared vs. having a plan, is similar to how Agile works.
Egyptian music: The band plays a song, and if you are familiar with it, you have ways to respond to it – but it isn't until the moment arrives that you execute the step. You don't think too far ahead because you don't know what the band will do. You are in the moment.
Agile: The team has a vision (see my Webinar on Iteration Zero), a goal, and a collection of prioritized stories, but each week they decide which stories really make sense to implement. Maybe your competition just announced something and you need to change your focus. Or else you need to add resources to get it done faster. The team responds in the moment to the problems at hand.
It's about being prepared to make the right decisions at a particular moment to achieve the end goal – a good performance or a good experience.
When I respond to music impulsively and instinctively, the audience usually has a positive response to the performance as feeling natural and fluid; not a choreography or a script. I make it "look easy." The same is true when I do a presentation just speaking to the points without a script. People tell me when I "just talk" that I sound more natural. When I read from a script, it sounds scripted – good, but scripted. Like I'm trying too hard. I'm not prepared – I sound too planned and executional.
In a project with a very defined plan, fixed deadlines and little flexibility, watch how your team acts. People are constantly stressed and are worried if the deadline will be met. The team stops focusing on quality and cares about getting it done now. There is little understanding about solving problems the right away, with flexibility and growth in mind. This is when band-aids happen and in the long-term you have spaghetti systems. No one ever goes back to fix these temporary solutions post-launch – they move on to the next thing. If someone prioritized what needs to happen to make a deadline and get things done the right way, the team would relax, focus on doing good work, and think of better solutions. It's more fluid – and a heck of a lot more fun.
Another way at looking at being prepared: when you drive a car, you are prepared to deal with different situations. If someone cuts you off and there is nowhere for you to go and you can't stop, you don't go looking for your rulebook to get some advice. You handle it on the spot. You just keep moving forward. Admittedly, usually you are pretty scared going through it and are shaky after – but you act in the moment.
There is great comfort in having plans and predictability. In the movie "The Dark Night," The Joker says:
I just did what I do best. I took your little plan and I turned it on itself. Look what I did to this city with a few drums of gas and a couple of bullets. Hmmm? You know… You know what I've noticed? Nobody panics when things go "according to plan." Even if the plan is horrifying! If, tomorrow, I tell the press that, like, a gang banger will get shot, or a truckload of soldiers will be blown up, nobody panics, because it's all "part of the plan". But when I say that one little old mayor will die, well then everyone loses their minds!
Although the Joker character is crazy – he has a point. Plans are comforting. They let you feel that someone, somewhere has control and has thought through everything that is happening. And you feel that you will be safe and successful because someone knows what will happen next. But honestly, is that the way plans really work? Is this really reflective of life?
I'm not saying there isn't a sketch of a plan – that's like saying you just dance without music or drive without any destination in mind. That's just wandering aimlessly. You always need to have some type of goal. What I'm saying is that you can't plan for every situation and you have to go with the music – or the situation – and have the confidence to work through it. New, unplanned requirements come up every day. New business and competitive things happen. And yes, that is scary. And you can't plan for any of it.
Agile is about being in the moment. What are the important features for this next iteration? What is needed? It's about the team having self-confidence to respond to the moment rather than create a plan and worry about stories three or more iterations ahead of time when honestly – it won't matter. The music of life and business will change what's going on.
High-tech Really Is Like High School
High-tech is a lot like high school, where everything is a popularity contest and everyone wants to be like the cool kids with the great parties, the fashionable outfits, and the hot cars (go to any high-tech company parking lot in Silicon Valley and tell me how many Ford Fiestas you find…thought not!). Being yourself usually isn't cool and those are the kids who end up being alone. A lot. It's much easier to join forces with other kids to be part of a clique. I think the only big difference between high school and high-tech is that in high-tech EVERYONE has a start-up of some sort and wants to be the next Stevie or Larry (more proof in this video)..but I digress.
In my daily work, I always hear companies trying to compare themselves to Apple or Google. Sure, they are market leaders, but it's definitely NOT the model for all tech companies worldwide. Branding a company is the same as branding yourself, or finding your own identity. Adults tend to do this when they see shrinks and life coaches or read a lot about how to get ahead. 16-year-olds typically model themselves after who they think is cool in class. I think we all know how that works out.
I thought it would be fun to breakdown the industry and some of the companies into which cliques they are in. If you disagree – feel free to pipe in and let me know.
The Popular Kids/The In-Crowd
Apple, Sony (in it's day – they are now like the prom queen girl who grew up, got married, gained 30 pounds, and had 5 kids with the football player who is now fat and bald. Playstation keeps this one going), LG, Philips, Samsung.
They have their unique quirks and all set trends, but generally are considered to be the innovators and the models for other companies. Sometimes they try to mirror the leader of the pack – Apple. (And I think Samsung knows how effective that is.)
The Jealous Girl
Microsoft is like the girl who wants to lead the popular pack of girls and is never quite able to do that. The girl who is pretty popular but always comes in second. Class vice-president. Runner up for homecoming queen. Runner up for prom queen. You get the picture.
The Bright Kids/National Honor Society
IBM, Panasonic, Brother, Lenovo, Canon and the like.
There are brands that aren't so sexy – but they have fairly reliable product and do ok on the market. These are the honor students – they create some products that are solid but not at the cutting edge of technology. You get them because you know you'll get something that looks ok but most especially works – kinda like what an honor student will do on a job. These kids will sometimes ask the Nerds for help (like Intel).
The Jocks
Software, Internet and mobile app companies. Think eBay, Google, Twitter, Facebook.
Their level of achievement is based on something beyond school and books. They rule the school, no doubt, but they are given more slack about academic performance (product performance). Facebook is like the C athlete – it's well known, does great on the field, but school performance (i.e. – as a product) – yeah. Google is like the A athlete – a smart quarterback that gets to date all of the girls in the In-crowd.
The New Kids
Amazon. Some of the new mobile phone companies or companies that deal with wireless technology.
There are those who changed – like Amazon – but essentially, they are new in high-tech. No one has really noticed them yet, and they have some time to get their own style or join one of the cliques. What great freedom!
The Nerds
The ones who wear the pocket protectors. They deal with the hard core issues and are marketed to the tech-heads. Their products typically perform well – and if they don't, they aren't around long (they get challenged by a fellow nerd and are either someone's man-servant or move to the loser category). They are also frequently asked by the jocks and the in-crowd for tutoring and help with class (partnerships).
The Artsy Ones
Adobe, Ninetendo, Apple, Microsoft.
These kids make things beautiful – and have beautiful products (iPad, iPhone, Wii, XBox). Or they have products that make beautiful things (Photoshop, Illustrator, etc.). They are the high-tech artists – and we all know it. And highly competitive (the rivalry between Adobe and Apple is now legendary, although they started as friends.).
I'm not that mean to give these companies the label that most would give them
Dell and another large tech company
For these companies – think the kid that has had a diet of cheetos for years, been playing too many video games, not going to class, and wondering why they aren't getting anywhere in life. Dell is pretty much having regular doctor visits to stay alive. Here's an overview of what's going on and some of the latest in the Dell drama.
The other company mentioned is undergoing a makeover for the prom – but honestly, that's just not enough. It needs a life change – I strongly suggest that it start going to the gym and stop snacking on those cheetos. Putting on better clothes, makeup, getting a nose job, and a stomach band won't fix severe weight gain and intestinal disorders. It has a pretty good report card for consumer and enterprise. It can go back to being in that in crowd, but seeing the results of hitting the gym and eating better takes time. But there is promise. Dell's lost – but this other company I'm thinking about may just make it.
There is room for everyone in the tech industry – but like in high school – the challenge is just being who you are. And honestly, what 16-year-old really does know himself? Maybe the industry just needs to grow up, become an adult and hire REAL life coaches (brand consultants) to help make these companies the men and women they need to be.
