A foundation for your design isn’t only created with happy thoughts and people high-fiving each other. It’s also based in a software project’s ecosystem.
Just like certain animals are highly adapted to the surroundings they live in, we have to adapt to the surroundings of software projects if our products are to survive. African wildlife has found numerous ways to deal with the desert heat. Sprinkboks have white underbellies to stave of the sun’s heat, Desert Foxes have huge ears, certain lizards are known to alternately weave on two legs to stop the soles of their feet from burning, Australian Kangaroos lick their paws during the hottest hours of the day to artificially enhance the cooling effect of perspiration. Nature find’s a way for every hardship her ecosystems heap on their inhabitants.
The Inhabitants of the Ecosystem
So we, as inhabitants of a software project’s ecosystem, have found a myriad ways to deal with different hardships. Tens of thousands of pages have been written on all kinds of subjects having to deal with every way a project challenges its participants. This website is nothing more than a combination of existing theories and other forms of information, mixed to create new insights into existing problems.
Almost always, solving problems is not about finding totally new ways of dealing with the issues at hand, but taking existing ones out of radically different areas than the one where the problem originally arose, and start applying them.
Through the years a lot of extremely intelligent people have spent decades to be able to put their thoughts into words. If we don’t use that vast amount of knowledge out there we’re idiots inventing wheels all over again.
“Free Will” and All That Jazz
The difference with animals and humans operating in their respective ecosystems is that we can consciously think about the way we operate, animals can’t. Animals don’t think, they just do. If there’s a stimulus, they respond in evolutionary fabricated behavioral patterns.Put a rat in a box with a tiny lever which, when pressed, procures a tiny morsel of food and you’ll find the rat start humping the lever like there’s no tomorrow. Chicks when born, immediately start looking for the first large object in sight. If that so happens to be you, you’ve instantly become their mom and they start following you. Humans are also a product of nature and we obviously have certain innate behavioral patterns, no doubt about it. Maybe even more than we like to think with our “free will” minded characters. But we are much more than our animal counterparts when it comes to free will. And that is that in each and every moment we consciously can make a choice about what to think about something. Richard Dawkins has written a classic which touches on this subject called “The selfish gene”. A book I highly recommend.
“Choice” and All That Jazz
Choice is something different than expectation about behavior. If I slap you in the face I can expect a certain behavior, but the recipient still has a choice. One that the majority of people won’t make, but I still remember a certain individual has said something about turning the other cheek. There will be people who’ll argue that they had no choice in a certain matter, they had to do this or that because of what person X or Y did. It’s that mindset that has created wars for centuries. A couple of people hijack four airplanes, fly them into two buildings and are able to rally the most powerful offensive force in the world. That didn’t just happen, at each and every step there were people on both sides making active choices about how to respond to certain stimuli and what to think about that. I remember discussing the subject of discrimination and racial bias with two colleagues, one being from Burundi and the other one of Surinam Hindu origin. The discussion went back and forth with me talking about choice and they about me not being able to understand what they had to deal with. It didn’t end there for the three of us decided to go out one night. So we had a few beers in a bar in this little town on the outskirts of Amsterdam. And I slowly began to “understand” what my colleagues were talking about. We were being unscrupulously ogled. When the bar closed we went to a local nightclub and there it happened. Not only my two friends had to show ID’s, for the first time in my life I had to do it. This had nothing more to do than me being with two black guys. And they were cracking up slapping me on the back yelling: “Now you know, now you know!” So we worked up an appetite doing these African dance moves and afterwards headed towards a Turkish diner. To my astonishment the owner of the shop told us standing behind the counter he was closing while behind us the seats were packed with white suburbia. My colleagues doubled up again when they saw my face. It must have had the dawning of bitter realization all over it. The lesson I learned is this: I certainly gained a profound understanding of my colleagues predicament in dealing with the very real Dutch racial prejudices first-hand. On the other hand, I didn’t change my mind about the ownership of choice.
Manage Your Expectations
The ecosystem has a lot to do with expectation and how to appropriately respond when what was expected is near e.g. what choices to make. I’ve seen my colleagues being frustrated about making software which was never used. But would you have the same level of frustration when I add that the end-users were never actively involved enough to the point when they knew when and where to act, and most of all why? Probably not. The only difference is that with the added knowledge you have a different expectation about the outcome.
How can you be frustrated about something you have the ability to act upon to alter its course?
Unfortunately a lot of people do, while they themselves could have made a different choice. Not with hindsight, but before thinks went awry. They had the knowledge, they had the ability, maybe even had the responsibility. The ecosystem and what it means, not only for you as a designer, but for all it’s inhabitants is not being able to say: “Ich habe es nicht gewusst.” I don’t claim that what happens during software projects is anything near what happened during WWII but denying involvement after bad things happened is the common factor.
In order for our software design to not only survive but thrive in a software project ecosystem we have to build that ecosystem. As humans we are the only creatures alive with this ability: the ability to shape our ecosystem. We have done so with nature, we can do the same thing with our software project ecosystem. Why we want to do that is to shape our moments of decision and manage expectations, two extremely important distinctions.
If we shape our moments of decision it’s very likely we actually make decisions and give ourselves the breathing space for constructive follow-up.
If we manage expectations we achieve the exact same thing, minimizing frustration.
Making choices, taking follow-up action and managing expectations are three key elements all flowing from an effective design integrated into a sound ecosystem. Although I might have discussed the ecosystem in rather vague terms, the following chapter is all about in-depth specific aspects of various part of the ecosystem. These parts go by the name of project “phases”.
Related posts: