• Skip to content
  • Skip to primary sidebar

Sazbean

Software Development Management

Main navigation

  • Home
  • About
You are here: Home / Archives for software development

software development

Aaron Worsham / Feb 26, 2009

What were they expecting?

the-conversationSucceed at managing your customers expectation and you can never fail.  Fail to manage your customers expectations and you can never succeed. ~ me

This is one of my all time favorite universal lessons I have gleaned from business.  There isn’t really any part of my life that involves other people which doesn’t benefit from the practiced art of managing the expectations of those I’m interacting with.  When another human knows exactly what they can expect from you, on your terms, and when you consistently meet or beat that expectation on their terms, you have set the stage for a powerful ally in business; trust.

The reason this is so important is because people on a whole are very self-referential, which means they see their own perceptions and actions within the conversations and interactions they have with other people.   Imagine two people talking business over lunch.  The speaker could say ‘it will be a short project that we can deliver with limited resources and for a reasonable amount of money’.  The listener will build context around the statements with their own assumptions, drawn from their own experiences of what is short, limited and reasonable, that will ultimately create very different picture than the speaker meant to convey.  At that moment, an expectation was set in the mind of the client that may or may not be ironed out in the contract negotiations but will greatly influence the customers satisfaction when the project is completed.

I worked with a fantastic colleague on the team that had a very bad habit of responding to challenging technical requests with an automatic ‘Not sure yet, but that should be doable’.  What he meant to deliver was ‘It SHOULD be doable, but of course I won’t know until I work on it” and what the customer heard was “That WILL be EASY and there is no reason it won’t be done on time”.  So when said colleague moved heaven and earth to deliver on what turned out to be a very difficult task, the customer was unimpressed.  They had already expected it to be done without effort and was maybe a little disappointed that the colleague didn’t work on some of the other, less important features.  This is what I would call a ‘Technical win and an Expectation fail‘

Here are some tools and tricks I use when working with other people to help set the expectation

  • Pictures and mockups.  When you are working in the web industry, their really isn’t an excuse to not mockup what you are seeing in your mind for the customer.  A tool I like to use is Balsamiq, which is a Flash based web mockup framework that is quick and easy to use
  • Agile Development.  The agile process focuses on rapid delivery of code, typically every two weeks, that gives the customer something to wrap their head around.  I think Ill do a full post on agile tomorrow
  • Closing summaries.  When I talk with customers, I have developed a technique of always closing out a conversation by saying ‘So, what I understand you want is…’ and just re-summing everything you’ve been talking about.  Etiquette might frown on dragging on a conversation past what the listener wants to endure, but I almost always find mismatching expectations in the closing summaries.

What do you do to manage someone’s expectations?

photo attributed to polandeze

Technorati tags: software, software development, software management, agile, agile development, customer-centric, customer service

Aaron Worsham / Feb 4, 2009

For 'Bleeding Edge' prepare to pay in blood

knife-edgeIf you are in software development, take a good hard look at the code you are writing right now.  If the string of Roman characters resemble Java or .Net or C/C++ then I have some wonderfully awful predictions about the next ten years of your life; That language is your scarlet letter and will follow/define you for the next two jobs you end up accepting.  That sounds bad but you are the blessed among the damned – You can and will find that next job.  For Bleeding Edgers, the road is not so well paved.

In my last job I was a Bleeding Edger.  You know one if you work with one, always looking at the latest release of the newest language to see if it has a better solution to your particular problem.   In my case as a Software Manager, being a Bleeding Edger meant an obsession with ROI in our software solutions.  Links to anything that could trim development time and/or expense filled my Delicious feed.  I pushed my team to move beyond Java’s heavy web frameworks and to adopt Rails as a rapid application prototyping framework.  We cranked out good, solid software solutions 4 times faster than our java days and I was happy.  When a project came along that could use Flash, we wrote it in Flex instead because knowing how this company worked, they’d want a desktop and an offline version in the future.  A year later we were cross compiling the Flex code into an AIR application and saving a tremendous amount of time, and we were happy.

But being a Bleeding Edger means there will be dark days to contrast the brilliantly sunny ones.   Our ROI figures were not enough to protect all of us throughout this economic upheaval and some would have to make the sacrifice for the rest.  I would like to say that, as the manager, I fell on my sword for them but that’s not really the case.  The decision never reached my level.  I was the highest compensated on the team and so I was killed by simple, cold math.  The blood spilled that day is still dripping.  It still hurts.

The software job market is a rigged system.  Heavyweights in the market put enough momentum behind enough Java and .Net and C/C++ projects that they can be considered perpetual motion machines.  A class hierarchy between Java and .Net, perpetuated by recruiters with a simple word match on a job board, stacks the deck against the Bleeding Edgers in the mainstream.  You are a Hatfield or you are a McCoy or you are an innocent bystander likely to get shot in the crossfire.  The mainstream is not a system able to help the Bleeding Edger.  Sure, there will be the occasional posting that isn’t in your location and is looking for some bizarrely specific, must have requirement that categorically eliminates all humans including the guy who originally wrote the book on the library they are using.  In the end, Bleeding Edgers need to work outside of the system.

For the young, there are no unemployed Bleeding Edgers only uncompensated open source code contributors.  If you have the ability to live on nearly nothing, working outside the system can be a very rewarding and ultimately fulfilling life choice.  For the responsibility burdened older generations, there are really only two options as a Bleeding Edger.  The first, and likely most chosen, is to re-assimilate into the collective; scrub your resume of all references to Ruby and Jython, and  Grail, prop up your sun certifications if you have them, and become a team player.  The rest of us Bleeding Edgers, the ones the economy hasn’t driven to ditch digging, will become the countries next batch of serial startup founders.  We will be easy to spot, just look for the scars.

Technorati Tags: code, ruby on rails, ROR, software, software management, software development, web development

Primary Sidebar

About Sazbean


Sarah Worsham (Sazbean) is a Webgrrl = Solution Architect + Product Management (Computer Engineer * Geek * Digital Strategist)^MBA. All views are her own.

Business + Technical Product Management

My sweet spot is at the intersection between technology and business. I love to manage and develop products, market them, and deep dive into technical issues when needed. Leveraging strategic and creative thinking to problem solving is when I thrive. I have developed and marketed products for a variety of industries and companies, including manufacturing, eCommerce, retail, software, publishing, media, law, accounting, medical, construction, & marketing.

Copyright © 2008 - 2025 Sazbean • All rights reserved.