Archive

Posts Tagged ‘management’

Functional Allocation V

Holy cow! We’re up to the fifth boring blarticle that delves into the mysterious nature of “Functional Allocation”. Let’s start here with the hypothetical 6 level allocation reference tree that was presented earlier.

Levels Of Abstraction

Assume that our company is smart enough to define and standardize a  reference tree like this one in their formal process documentation. Now, let’s assume that our company has been contracted to develop a Large And Complex (LAC) software-intensive system. My fuzzy and un-rigorous definition of large and complex is:

“The product has, (or will have after it’s built) lots of parts, many different kinds of parts, lots of internal and external interfaces, and lots of different types of interfaces”.

The figure below shows a partial result of step one in the multi-level process; the Shall-To-Feature (STF) allocation process. Given a set of 5 customer-supplied abstract “shalls”, someone has made the design decisions that led to  the identification and definition of 3 less-abstract features that the product must provide in order to satisfy the customer shalls.We’ve started the movement from the abstract to the less abstract.

Just imagine what the model below would look like in the case where we had 100s of shalls to wrestle with. How could anyone possibly conclude up front that the set of shalls have been completely covered by the feature set? At this stage of the game, I assert that you can’t. You have to make a commitment and move on. In all likelihood, the initial STF allocation result won’t work. Thus, if your process doesn’t explicitly include the concept of “iterating on mistakes made and on new knowledge gained” as the product development process lurches forward, you’ll get what you deserve.

stf example

Note that in the simple example above, there is no clean and proper one-to-one STF mapping and there are 2 cross-cutting “shalls”. Also, note that there is no logical rule or mathematical formula grounded in physics that enables a shallocator (robot or human) to mechanically compute an “optimum” feature set and perform the corresponding STF allocation. It’s abstract stuff, and different qualified people will come up with different designs. Management, take heed of that fact.

So, given the initial finished STF allocation output (recorded and made accessible and visible for others to evaluate, of course) how was it arrived at? Could the effort be codified in a step-by-step Standard Operating Procedure (SOP) so that it can be classified as “repeatable and predictable”? I say no, regardless of what bureaucrats and process managers who’ve never done it themselves think. What about you, what do you think?

Productivity Lag II

In part I, we saw that the learning curve for each person is different (duhhh). I also defined the Critical Mass Time (CMT) to be the time lag between starting a new project and actually being able to “start contributing something useful”. The figure below recaps this idea.

productivity 1

Other factors, besides experience and expertise, that determine the CMT value are: the amount of, the quality of, and accessibilty of pre-existing information about the problem to be solved. If the information is sparse, fragmented, and/or inefficiently stored in other people’s fallible memories (tribal knowledge) because of the failure of management to lead, then the CMT will be larger than if  the critical-to-success information is coherent, integrated, and recorded somewhere that is easily navigable and accessible.

At the CMT point, productivity starts manifesting in the physical world as visible intermediate work outputs. Product specifications, designs, test definitions, equipment assembly, prototyping, model definitions, etc., begin to emerge and push the project forward. Like any activity that is predicated on fallible human thought, the creation process is iterative and chaotic. It is not smooth and organized as the final output may imply to an after-the-fact external observer (like most managers). It takes iterative, mistake-prone work and structure to temporarily harness the ever present increase in entropy.

The figure below shows the full time lag between project start and project completion. Again, the time lag ‘tween CMT and project “done” is highly person-specific.

One And Done

The figure below shows the end-to-end project start time to project done time for three different people that were given the same project task to perform. The difference between the total “schedule” performance of person 3 and person 2 is the case we want to zoom in on. How could it be that person 2 ramped up faster than person 3 but finished the project later? WTF?

Three And Done

Some reasons that may explain this anomaly are:

  • Person 3 had a hard time finding and absorbing high quality, pre-existing information about the project and task at hand.
  • Person 3 is slower at learning, but more talented at applying.
  • Person 2 lost some motivation for one or more reasons and slacked off somewhat
  • Person 3 rushed through the task and produced crappy output that may not be discovered until the project is further downstream; where the cause might not be connectable to the person’s output.

I’m sure that there are a gazillion other factors that may explain the anomaly. You can form your own list.

The main point of this article was to discuss what everyone knows, but often forgets: Numbers don’t always tell the truth. Superficially looking at hard and cold “schedule performance” numbers without digging in to examine their validity can be unfair to those who are quantitatively measured for personal performance evaluation by hierarchs. Lazy bozo managers who do this deserve what they get: the exodus of some of their best performers, an unmotivated workforce, a low quality product portfolio, and an unfair reward system. In essence, it’s one of the hallmark characteristics of the herd of mediocracies that cover the landscape of the business community.

Productivity Lag I

Each person naturally has a different learning curve. When an engineer is assigned a new task to perform on a new technical project, there will be a lag in productivity because, well,  it’s new to him/her. The person needs time to learn and understand the context surrounding the project and the details of the problem to be solved. Since each person is different, each person will have a different time-to-productivity, or Critical Mass Time (CMT). The graphic below shows a typical learning curve for a specific person. The slope increases with time because as new learning occurs, it feeds on itself and the acquisition of knowledge gets easier.

productivity 1

The CMT is a physically underive-able function of the experience and expertise (two independent qualities) of a person. It is also a function of the area of overlap between those two attributes and the novelty/depth of the problem to be solved. As the figure below shows, the person-specific CMT is at its minimum when there is 100% overlap. Note that if there is no overlap, the CMT is essentially infinity. This sad state can happen, for example, if a Radio Frequency circuit designer is assigned the task of designing and writing product software, or a plumber is assigned to perform brain surgery, or an enterprise IT software engineer is assigned the task of writing embedded signal processing software. It’s easy to find other examples of total mismatch.

productivity lag

Assuming that the experience and expertise of each person in a group of people overlaps somewhat with the project task that needs to be performed (no cases where CMT = infinity), the graphic below shows how CMT differences within the group can vary radically. Obviously, if you were a manager, you’d like to have Person 1 working the problem.

productivity 4

So what happens when an executive manager or marketer commits the company to a scheduled project completion date without knowing the learning curves of his/her people, or the difficulty of the problem to be solved? As the figure below shows, blown schedules occur. Before (and after) the schedule is missed, increasing pressure-to-complete is continuously exerted by management, mistrust grows, and the employee-management relationship suffers. Of course, since management is (at least) one level removed from the action and they don’t have to perform the task themselves, they are blameless. Because of the FAE, the employee, of course, is fully at fault and a “performance improvement” plan may be in order. If an employee ruffles feathers and dares to publicly point out the mismatch, accusations of “not being a team player“, “malcontent“, and/or “bad attitude” are the thanks he/she gets. If the employee persists, the ostracism may be followed by a stronger message to STFU – a required trip to “people-skills school“.

commitment

This pattern of dysfunctional behavior occurs so often in hierarchical corpos across the land that it is taken for granted and it is “undiscussable“. It is also one of the reasons why people do everything they can to get out of the pig sty and climb the corpo ladder to succes. The further away from the action you move, the higher the chance that  you’ll be sanctioned by the big boys(gals) to convert from a pressure-receiver into a pressure-exerter. As an added bonus, you’ll make more money because of your “increased responsibilities” (sic).

Reconfiguration

Understandably, companies that achieve success in a business area strive to maintain the behaviors that got them there. However, as they work to continuously stabilize themselves, the external world keeps changing around them. Sometimes the change is gradual, and other times it’s instantaneous and explosive. Regardless of the rate and magnitude of change, if the company does not adapt to the new external situation, they’re hosed.

Two Paths

“When you’re through changing, you’re through.” – Bruce Barton

Two Paths

“Without deviation from the norm, progress is not possible.” – Frank Zappa


Categories: business Tags: , ,

One Level Removed

July 10, 2009 3 comments

Assume that you’re on the third level or higher in a hierarchical corporate (dis)organization. If you want to know what’s really going on so that you can take action to keep improving the org’s performance, ask the people below you, one level removed. Do it frequently, and do it periodically. If you have lots of people that indirectly report to you two levels down, you could listen to their inputs in small groups or, even better, randomly pick a different person every week to listen to.

One Level Removed

Why should you do this? Since you hand-picked your direct reports and you directly control their salaries, they’ll naturally tend to distort the truth if it makes them or you look bad. You’ll tend to unquestioningly believe them just so you can continue to feel warm and fuzzy inside. If you don’t have a machismo culture of fear that hierarchical structures auto-instill into the lower segments of the org, then at least some of the courageous people two levels down will tell you the truth as they see it. Otherwise, they won’t tell you anything of substance, so don’t waste your time trying to find out the true state of things.

Why don’t most managers frequently survey those people one level removed? Because as one rises up the corpo ladder: they usually get lazier, they get disconnected from the real work that creates and sustains value, and their head expands. Bummer.

“The day soldiers stop bringing you their problems is the day you have stopped leading them. They have either lost confidence that you can help or concluded that you don’t care. Either case is a failure of leadership.” – Karl Popper

Categories: business Tags: , ,

Boomerang Effect

Be careful. Be very careful. If you’re at the bottom of the corpo pyramid, don’t even try to break the status quo. Maintaining the status quo in a staid corpo hierarchy is the number one priority of the people at the top of the pyramid. Why? Because they’re at the top, and they’ll do anything to stay there. It doesn’t matter if their actions, or lack thereof, keep the company’s existing products and supporting infrastructure in the dark ages or erode profits, they’ll ensure that they stay on top. Period.

The only thing that a stratified hierarchy is fast at, is fending off attempts to, and squashing ideas designed to, help the company improve. Even if a major idea does somehow miraculously get initiated from the middle or the bottom, as soon as the hierarchs realize that it may result in sweeping change, the crumbling pyramid will do an auto-realignment. Just like that flexible molten metal robot from Terminator III.

To top it off with an exquisite cherry, the top managers will set an example of the poor soul(s) who started the move toward change. The graphic below shows what usually happens. You don’t want to be the guy or gal who tried to kick the field goal 🙂 .

Boomerang

FAI = Frontal Assault Idiot

July 4, 2009 3 comments

Since I already have a post regarding the FAE, why not supplement it with one on the FAI?

The other day, my friend and mentor, Bill Livingston, rightfully and truthfully called me an FAI. The picture says it all. No more words are needed, except for: “poor me, boo hoo”.

Wannabe

Everybody wants to be a manager or director. Hell, why not? Extracting yourself from the pig sty of hard and sweaty work that directly creates value is the smart thing to do in an obsolete org that is structured as a stratified pyramid. And, how many orgs do you know that aren’t structured as outdated command and control hierarchys? Subjectively of course, I assert that managing and directing others ( fancy words for command and control) is easy relative to doing hard work and constantly getting beat over the head with the schedule stick. Plus, it’s pays more, and you get to have some fancy title of superficial importance appended to your name. Oh sure, you have to put up with whiny direct reports (like me 🙂 ) but does that really warrant more pay and value by fancier and higher paid people positioned even higher up in the pyramid of woe?

I respect people, not titles. If you, as an anointed and highly compensated manager or director:

  • listen to your people and treat them as equals,
  • actively and visibly help your people get their jobs done better and better each day ,
  • pay for ongoing training that’s critical to the company’s future success,
  • constantly and diligently take action to repair decaying infrastructure as a result of increasing entropy (2nd law of thermodynamics)
  • don’t act two-faced (e.g. pounding your people with schedule while espousing “quality is king”),
  • behave congruently and with integrity,

then I’ll respect you and the title that you rode in with. Otherwise, fuggetabout you, your fat head, and your fancy title. Other people, out of the natural fear that all pyramid org structures auto-instill into the minions at the bottom, may feign respect, but I won’t. However, being human, and (hopefully) not too stupid, I do publicly kneel and pay homage to the awesome power to instill fear that is naturally built into the hierarchy – most of the time. Since “most” is not the same as “all”, you can use your imagination to envision my day-to-day experience in a hierarchically structured workplace.

Being a software designer, I’ve learned that different structure types enable or disable different types of behavior. The pointy haired hierarchy, with it’s long history of top down command and control misery, is a disabler of highly creative, adaptive, and efficient human behavior. Since humans (especially those in western countries) are mostly about “me and my story”, and those at the top always accumulate riches at the expense of those at the bottom and on the outside, the pyramid of woe won’t be going away soon.

Regardless of the amount of damage inflicted upon those at the bottom and to external stakeholders, the people at the top will continue to wield their power to keep themselves entrenched. Why continue this irrational behavior? In order to continue living the high life of luxury and consumption, of course.  However, the relatively flat network structure fueled by the rise of the internet, will eventually displace the collapsing corpo C & C hierarchy in the future. Those that wait too long will die. Too bad this global maelstrom of change won’t happen in my lifetime.

Ineffective Immediately

July 1, 2009 2 comments

“Ninety percent of what we call ‘management’ consists of making it difficult for people to get get things done” – Peter Drucker

If you believe this classic Drucker quote to be true, then whenever you receive an executive e-mail that contains the standard MBA textbook words “effective immediately”, mentally replace them with “ineffective immediately”. That way, you won’t be disappointed or surprised when your local work environment doesn’t change at all, or it changes for the worse.

To be fair, managers, like you and me, are just trying their best to make things better for all stakeholders. It’s just that they, for the most part (90% to be exact) have no clue on how to go about doing that.

Schedule Policy

Sched Allegiance

Just about every corpo mediocracy in the world has a proverbial “Quality Policy” that it proudly displays all over the place. The inspirational words of wisdom, that hierarchs profess staunch adherence to, are inscribed on framed posters, and/or cute little magnetic sheets. These false idols are distributed far and wide within the cathedral walls for everyone to worship.

However, everyone down in the boiler room knows that the true corpo allegiance is to schedule. How do the serfs know this? It’s easy, and it doesn’t require an Einsteinian intellect to figure it out. Just walk around the cubicle farm and count the number of times you hear managers mention the word “quality”. Then count the number of times that you hear “schedule”. Voila, you then have your answer, and it doesn’t involve rocket science math. Companies that have higher schedule to quality ratios are much more likely to fill the ranks of the average and boring herd.

Schedule worship, at whatever the human and organizational cost, is one of those issues that Chris Argyris calls “undiscussable”. Anyone who points out the fact that the quality policy is actually a lame attempt to camouflage the true and unconditional allegiance to schedule, gets beheaded in true shoot-the-messenger form. Nobody in their right mind “discusses” the quality versus schedule irony because, well, it’s “undiscussable”.  🙂

I propose that all companies develop, distribute, and display their very own authentic schedule policy. One could go something like this:

“The Duefiss corporation is proudly dedicated to meeting schedule. Our allegiance is unconditional. At Duefiss Inc., we will aggressively cut every corner and apply any amount of pressure to our human resources to meet any schedule. It doesn’t matter how laughable or unrealistic  any given schedule is. We will commit our minions to it, no matter what the consequences to them, their families, our product quality, or our long term credibility and profitability. When we fall behind the hallowed schedule, we guarantee to turn up the heat on those responsible for the slip, and increase the frequency of status meetings to reinforce our commitment.”

What would your schedule policy be?