Posts Tagged Design Thinking
I recently completed a 3 year project which – according to client requirements – should have been done 2 years ago. Hey, I’d like to say that good things take time! But the truth is that sometimes life – and IT project execution – is just unpredictable. And painful. But – ever the optimist – throughout the three years, I tried to find the sunny spot in the gloom of our basement project room. And today I’m asking myself “what did I learn?”
You cannot deliver on something you do not know.
Seek out experts, get training for yourself and your team. Classroom training is not enough. For me, I learned the most from my network of connections I had built over the years through my engagement in a professional community – the Americas SAP Users Group (ASUG). Collaboration with others outside of my own usual comfort zone – across companies and within my own company – helps me to shift paradigms, and, in this case, helped me to question my own design and to rethink the possibilities.
Expectations are sneaky.
Expectation – noun – a belief that someone will or should achieve something. We IT people like things that are concrete – you know, “If x, then y, else z…”. As Project Managers and Business Analysts, we follow plans and processes, carefully sequenced and timed. We define scope and lock it down. What is impossible to manage are the expectations of a variety of stakeholders – each with different concerns. In my case, Legal wanted the solution delivered fast. Business areas didn’t want productivity disrupted. Administration wanted something that would require little manual intervention (add time to the project plan here!). Human Resources wanted a solution that employees would like (add more time to the project plan). IT, of course, wanted us to stay on time and within budget. I understood all these expectations. What we missed was how difficult it would be to keep those expectations from creeping back into the project even after we had all agreed some things would simply not be done within the parameters of this project. There’s only one way (in my humble opinion) to prevent being sidetracked by expectations: that is, have one single person as the ultimate decision maker.
“Failure is delay, not defeat.” – Denis Waitley.
Despite your best laid plans and past successes, sometimes you simply fail to meet everyone’s expectations, the timeline or the budget. But I refused to admit defeat. We missed the two scheduled release dates. We went over our original budget by a significant number. Despite the pressure from management on those two points, our team persevered in finding the right solutions. With my sense of integrity intact, I suggested a redesign of the solution – thereby removing many of the hurdles that were getting in the way of expectations — some of which were pretty important expectations. No one applauded or sent bonuses my way when we were done. But I have the satisfaction of knowing I did the very best I could and that what I delivered really did remove potential issues for our buisness.
Denis Waitly said “Failure is something we can avoid only by saying nothing, doing nothing, and being nothing.” I don’t think I can be accused of any of that. The entrepreneurial spirit in me still prefers to challenge the status quo, longs to innovate, and is okay with taking a calculated risk. I have raised two daughters who were at times scared to fail. And everyday, with every new decision they faced, I would say, “What’s the worst thing that’s going to happen if you try that?” I have never received an answer to that question from either one of them. And so now I am going to take a page from my daughter’s playbook at Blondes Have More Run and leave us all with the following.
Excuse me now, but i have to keep going!
In my early 20’s, I was incredibly serious about how others viewed me and whether or not I was being taken seriously. At a friend’s picnic, someone sprayed me with a hose and I was upset because my hair was ruined and my cute outfit had to be taken off to dry. Seriously.
I have been taking that perfectionist attitude to work too. EXCELLENCE demands getting it all absolutely 100% right – right? I mean, you agree, don’t you?
Here’s the thing that working in technology taught me: the 80/20 rule. Sometimes you have to sacrifice something to get to the bigger picture. If your budget is tight and timeline is short and only 80% of the business requirements will be met, can the 20% be handled in another manner?
For those of us who are perfectionists, this is difficult to accept. You have to step back and see the entire view. How much more money will it cost to do it “the right way?” And – as rapidly as things change in today’s world – how long will your “right” design be relevant? What are you really trying to fix? Really dig deep and work together to understand the core issue. Sometimes the answer to the problem is much simpler than you initially thought. Sometimes, there really isn’t an issue at all – but a perceived issue or a misguided process.
Most days I still dress pretty impeccably for work, believing in the mantra dress for the job you want, not the job you have. As I raised my two daughters, however, I cannot always afford to be as impeccably dressed as I would like. But, I’ve learned that it really doesn’t matter what my hair or clothing look like if I am not bringing quality and productive results to the table.
In a large organization, we’re all in it to make money — and not just for ourselves, but for the company. When the company we work for wins, we all win.
“How Design Thinking is Making ERP Software Better” is featured on Page 78 in the May issue of CIO REVIEW. After proudly posting this picture on Facebook, one tech friend (@MicoYuk) tweeted in response “YES!! I LUV to see women on top of their IT game. Congrats to @SherryanneMeyer for bng featd in @CIOReview p 78 #WIT http://www.cioreview.com/magazines/may14/SAP2014/ …” I realized – remarkably – that the publication was a bigger deal than my byline. I went back into the magazine to check the conributors. I counted males and females. I was one of only 3 women who contributed to that issue of the magazine.
I want to be clear: I do not think the lack of female contributors is because the editors overlooked female candidates. I think it’s because women who are willing to put themselves out there are harder to find. I have a sense that when women draw attention to themselves it is not well received, and that therefore, women avoid opportunities that may shine too bright a light on them. Being vocal as a female is a fine art requiring delicate and adept balance to avoid inciting resentment among one’s peers. (I don’t know that I have mastered that art yet.)
Mico’s tweet to me made me sit up and take notice to how many of us are not leaning in to speak our minds on the broader technology platform. Nearly everything I’ve been taught has come from textbooks authored by men. Nearly every speaker I have had the pleasure to hear at a technology event has been male. And I checked who I follow on Twitter, and – GUESS WHAT!? – of the individuals I follow (not organizations), the majority are men.
Why is it that women don’t step out, say more, get quoted, write, speak, or publish more? Is it too risky to “Lean In” to put your thoughts in writing? Are we too busy being wife, mother, friend and tech genius all at once?
My Point of View: We need to be heard for the generations of young men and women who follow.