Business is indifferent to individual readiness for conducting it diligently! In other words, there are numerous ways to mess things up. Witness and testimony thereof can be found in nearly all aspects of life. Just reading the daily news will certainly substantiate that statement.
Without delving much into topics like politics or economy, both of which are oblique to your ability of making an instant and/or substantial impact, you have plenty of opportunity to regularize the everyday chaos by adhering to a set of rules. Usually this is where someone would reference a smart book they read. So am I, but whilst its not the holy grail, there are good ones in here (mind you, the guy who wrote this is controversial as hell, and I do not endorse or share his agenda by posting a link. He just set out, in parts, a nice framework to address chaos, which is my utmost concern and foundation to this blog)!
Why am I the right person to teach others how to avoid chaos in software, operations or business development? Frankly, I sometimes for myself, whilst in the process, find it disturbingly obvious that I am much capable of doing so, without being able to fully explain that virtue. I however can explain some of the elements contributing to it:
- To start off with, I am not young enough to know everything, hence I am much aware of what service I am able to deliver and I openly communicate about it!
- I have been in executive positions for more than a decade, perpetually mastering difficult situations that require a lot of skill and patience.
- Out of all the ones conducive to the matter and which I could comfortably infer, this one is probably the most powerful argument! I am in the nth iteration (where n equals 5 or greater) of seeing problems resurface in a slightly different shape or format, but equally at its core. I have successfully worked out solutions in the past and present, each time improving by experience.
Prior starting this blog, I felt a strong desire to share cases that helped me build my knowledge base and character. I have long thought about the format I would like to deliver that knowledge to interested audiences. When I write, I love sarcasm, which makes it a lot more fun. Most of my articles will take the piss out of the cases merit, just for the sake of adding an entertainment layer to an otherwise boring occurrence (boring is of course relative to the level of average excitement the audience is usually experiencing in their everyday life).
I have thus structured my cases along a few cornerstone categories that need some explanation.
- Fundamentals: I will reference those posts quite a lot. The idea is to find an axiomatic approach to identifying chaos by validating case-based signals against the schema highlighted therein.
- Toolchain: The evidence for adding more chaos in software development by introducing a project management system or other tools as opposed to not having them is overwhelming. I have thus dedicated a whole category for this topic.
- Chaos: When things went south, it’s much harder to get them back on track, yet it’s not impossible. Here you’ll find important techniques to get it done based on real life stories.
- Humphrey & Mortimer: This is a pure but necessary persiflage. Case in point we are talking about consultants to your business. There are ways to make use of them in a reasonable manner, but they are generally of limited use b design. In this blog, Humphrey represents a well-educated and rhetorically trained spin doctor whilst Mortimer is an almost noble and extremely experienced networker. Both of them have one toxic thing in common, …, if you don’t guide or follow their actions closely, they will be of no help and cost you a fortune. For the purpose of this blog, I might use the word “insultant” instead of consultant occasionally.
In pursuit of generating some real-life value, this blog is dedicated towards making business and development better by introducing knowledge and patterns that shall help my audience to handle unknown situations and excel when stress and chaos unfold.