Archive

General

17 Ways To Piss Off New Hires Before They Even Start

I’ve hired a lot of folks in my time, and been through quite a few hiring experiences too. I’m always amazed that hiring organisations seem utterly oblivious to the tone they set for their relationship with new employees – even before they make the job offer.

Here’s a list of some seventeen ways I’ve seen organisations piss off their new hires even before those folks turn up for their first day:

17. Give the impression that mistakes are not tolerated in your organisation.

In particular, make it clear to candidates that hiring mistakes are career-limiting, and you and your organisation take great pains to avoid such mistakes. From this, candidates can easily infer what to expect when they actually start work.

What to do instead: Convey your willingness to take risks, and attribute that to encouragement from the organisation, rather than to any personal heroism. In particular, express the organisation’s willingness to stick it’s neck out for what it believes might be good hires, even when not at all obvious.
See also : Make Bad Hires

16. Make sure your communications are garbled through one or more intermediaries.

When little hiccups happen, make sure the explanation is garbled to the extent that any fair-minded person might interpret it as ineptitude, or even better, mendacity. This can go a long way to setting the tenor of all subsequent interactions with a candidate.

What to do instead: Communicate clearly to intermediaries that they are NOT expected to sugar-coat or otherwise alter the messages they relay from either party. Ensure all communications are available for inspection by all parties. In particular, don’t communicate by phone, and follow up face-to-face conversations with a written summary of what was said.

15. Talk exclusively about the current situation.

Assess candidates on the present needs of the organisation – after all, things aren’t going to change at all, are they?

“A good hockey player plays where the puck is. A great hockey player plays where the puck is going to be.”

~ Wayne Gretzky

What to do instead: Focus on the future. Any useful candidate will be looking to build a future with your organisation. Talk about how things are likely to evolve, and the challenges everyone will face coping with that. Explore how the candidate’s mindset, talents, skills and abilities will be useful in that possible future.

14. Appear uncertain as to why you’re hiring for this position.

If you know the value-add of the position, refrain from mentioning it. Better yet, talk with candidate from a position of genuine ignorance.

What to do instead: Realise that candidates would prefer being given “a good job to do” – i.e. one where the value-add of the position is clear and achievable. Go out of your way to gain an understanding of how filling this opening contributes to the goals of the organisation. And then communicate that. Better still, explore the value-adding possibilities jointly with the candidate.

13. Give candidates cause to believe you and/or your organisation are not serious players.

Don’t make any mention of established know-how, or initiatives to make things better. Skip over topics such as personal development, morale, continuous improvement, and such like. Never mention the “giants” in your industry (e.g. in software don’t mention folks like Deming, Ackoff, Seddon, et al.) and feign ignorance of bodies of knowledge relevant to your industry (e.g. Coaching, Team-building, Scrum, Kanban, Lean, TPDS, etc.). Gain bonus points by appearing oblivious to management-related bodies of knowledge too (cf. Buckingham/Gallup, Drucker, Deming (again), Hamel, Google, etc.)

What to do instead. Briefly touch on the bodies of knowledge the organisation has taken on board, and make a few mentions of specific cases of how the way the work works has been influenced by these bodies of knowledge.

12. Imply candidates will stand a better chance of getting the job if they lie.

Candidates who want the job will says what they think you want to hear. They will “creatively” tailor their CV or resume to the job specification if they believe that will improve their chances of getting hired. Never make this implication explicit! It, like so many of the assumptions and unwritten laws governing hiring, are undiscussable.

What to do instead: Act with integrity. Folks can recognise that, as they can a lack of integrity, dishonesty, and dissembling.

11. Keep asking them to come back time and again.

Make it seem like you couldn’t organise a piss-up in a brewery. Fail to line up in one session all the folks who the candidate will need to meet. Have them come back three, four, five times just to see another face who, most often, will make it clear through their demeanour and body-language that they were not so interested in meeting the candidate anyway.

What to do instead: Arrange all meetings, conversations, etc. for the same visit. Realise that more meetings and conversations add little to the validity of hiring decisions, and can give candidates the impression the organisation is risk-averse (see point 17. above).

10. Make the hiring decision appear arbitrary.

Make it clear to the candidate that it’s your decision who gets hired, and you have certain opinions which any candidate must match up to. After all, you’re in charge of your little piece of the organisation, and hiring folks on the basis of what’s good for the organisation just wouldn’t do at all.

What to do instead: Explain the criteria the whole organisation uses to assess candidates, and the special exceptions you (or the hiring manager or group) make to those general criteria.

9. Use formal interviews.

Don’t fall for all that scientific malarkey which shows how fallible humans are at e.g. making hiring decisions, and the research which highlights the universally poor results obtained through any formal interview process.

What to do instead: Skip directly to having likely candidates come in and do real work with real people, to gauge their fit. Pay them for this – and pay them to leave if they feel they don’t fit in.

8. Have an insane amount of paperwork.

Make sure that there’s a mountain of paperwork for each candidate to fill in. Make sure as much of it as possible is obviously unnecessary. After all, candidates would like to realise that 80% of their time is being wasted even before they start the job – just as it will be after – wouldn’t they? And stress them out even before the job starts with worries about their references, etc. being good enough.

What to do instead: Work with e.g. HR to ruthlessly prune the prerequisites for candidates down to a bare minimum. Provide them with a third-party service, similar to a concierge or such, to do the lion’s share of that bare minimum. Make it policy that no candidate may start before these prerequisites are completed. Place a time limit on how long such work can take – with a “free pass” after the cutoff.

7. Appear inept.

Look as if you’ve never interviewed before. Have a list of “typical interview questions” that sound like you found them online. Give the impression that you and your organisation are doing the candidate a great favour by even deigning to speak with them.

What to do instead: If you really have never interviewed before, admit to it. See if the candidate can help. If you do have some prior experience, appear to have learned from it.

6. Fail to understand or explore the candidate’s value-add.

Candidates are ten-a-penny these days. You’ve got a slot to fill, and you need a warm brain to fill it. Simples. No one is going to criticise you for not getting the best out of the folks you hire – at least, not if you appear to drive them hard.

What to do instead: Just about everybody wants to do a good job. Which means just about every candidate has put a deal of effort into developing their skills, learning things, and making the most of their talents. And they’d really, really like to apply as much of that as possible to the benefit of your organisation. So explore what they can do, and more importantly what they could do, given sufficient support and encouragement.

5. Don’t prep. Don’t help the candidate to prep.

If your interactions with a few of the candidates go awry through your being unprepared, well, who’s ever going to find out?  And if a candidate objects, well they’re obviously not of the right stuff, are they? And hiring is a bit like school, isn’t it? “Sit still. Don’t talk. Do you own work. Don’t copy.” So don’t help them to be best prepared, either. After all, if they’re really interested they’ll spend days of their own time doing their own preparation, won’t they? Besides, it’s a good introduction to what working here is really like. Best be honest, eh?

What to do instead: Show that you and your organisation respect people by being obviously prepared for each candidate. Not just having a prepared list of questions or check-list, but being prepared for each individual candidate, like they were a human being or something. And help each candidate present themselves in the best possible light by helping them prepare, even before meeting you and others.

4. Exclude the CEO.

God forbid your higher-ups taking any kind of interest in who you hire. That could be career-threatening. Better by far to keep all hiring activity to yourself. What possible benefits could there be to either the candidates or the organisation in being open about these things?

What to do instead: Invite your CEO to spend a couple of minutes, one-to-one and in private, with each near-hire candidate. See “The Four Obsession Of An Extraordinary Executive” for a passle of reasons why this might be a good idea.

3. Involve HR.

You’ll need someone to blame if things don’t work out. HR makes the perfect patsy, so get them involved as early as possible, and make sure they have a real say in the hiring decision – and not just as administrative support.

What to do instead: Make use of HR as administrative support, to ensure all the ‘I’s are dotted and ‘T’s crossed, but for God’s sake keep them away from hiring decisions, and from the candidates.

2. Don’t involve others such as potential colleagues and peers.

Show your cojones by appearing to take all the risks of the hiring decision upon yourself (but see also point 3.) Real managers don’t work via consensus, in any case. And the successful candidate is going to be your boy (or girl), aren’t they? Why would they need or want to meet anyone else before joining?

What to do instead: Solicit the opinions of some or all of the other folks involved. Have them meet the candidates for a chinwag over a beer or a pizza.

1. Ignore the candidate’s blog, twitter feed, LinkedIn profile, etc.

Social media? Pah! What possible use could that be? Besides, you’re busy – too busy to read all the lame stuff that candidates have been writing. Much better to ignore their paltry attempts to present themselves, their value-adds, their ideas and their personalities. Your innate talent to gauge an individual’s merit needs no supporting information. Besides, the best candidates are insular, uninformed, anti-social, inarticulate, unopinionated and easily influenced, aren’t they?

What to do instead: See if each candidate has a blog. Read a few posts which catch your interest and discuss them during your face to face conversation(s). Dip into their Twitter stream, if they have one, to get a feel for their personality, sociability and standing in their professional communities. Check out their LinkedIn and GitHub profiles and community contributions. And invite others in your organisation, that may also meet candidates, to do the same.

Of course, there are dozens more ways you can piss off folks once they have joined, but here we’re just talking about before that first fateful day. Why not use some or all of the above tricks to sour the budding relationship and set folks up to fail from the very outset? Millions of companies can’t be wrong!

“Most of what we call management consists of making it difficult for people to get their work done.”

~ Peter Drucker

Did I miss any ways that have pissed you off?

– Bob

Afterword [8 Oct 2021]: The most significant point, and not listed above, may be to share with the candidate that their contribution, however awesome, will only account for some five percent of their productivity.

0. Ignore the role of the system (the way the work works)

Make it plain to the candidate that result are entirely on them. Their commitment, passion, skills and effort is what really matters, and will be the basis upon which they’ll be judged.

What to do instead. Explain you view – and the organisation’s view – on Deming’s 95:5. Elaborate on the system in place, the way the work works in the team or department they’ll be joining, and who owns the several aspects of the way the work works. Make It plain as to the basis upon which their personal contribution will be judged.

Further Reading

Eight Hiring Mistakes Employers Make: From Application to Interview ~ Susan M. Heathfield

Mañana

Obviously there are going to be days, or even weeks, when a team is necessarily focussed on delivery. Sponsors and Product Owners have deadlines, the world dances to its own drum, and sometimes it’s a struggle to meet those critical dates.

At times like these, attempting to also focus on longer-term improvements – such as building trust – can just add more stress, and seem to detract from the task at hand.

So, mañana becomes the default response.

“When will we talk about morale?”
“Mañana.”

“When will we invest some time in sharpening our saw?”
“Mañana.”

“Can we do something about our level of capability to deliver?”
“Mañana.”

“I’d like more predictability, lower costs, more responsiveness and higher quality.”
“Mañana.”

And so on.

How does your team find the balance between the demands of today, and mañana?

– Bob

Further Reading

LEGO, Square Wheels, Innovation, Leadership and stuff ~ Dr. Scott Simmerman

Local Optima

I’ve heard that a picture is worth a thousand words. And more recently, some research has shown that information presented visually has more likelihood of convincing.

So, here’s a chart. It illustrates relative effectiveness of the different approaches to e.g. developing software products and systems. The X-axis is the relative effectiveness, increasing towards the right. This same axis also maps from a narrow, local focus on parts of a system (left-hand side) to a broad, global focus on the interactions between the parts of a system (right-hand side).

Note: This chart represents aggregates – any given development effort may show some deviation from this aggregate. And also note, we’re talking about effectiveness from the broader perspective: meeting customer needs, whilst also satisfying the developers and other technical staff, managers, executives, sales folks, suppliers, etc. – i.e. all stakeholders. I also assume the aggregates exclude LAME, Wagile and other such faux approaches where folks claim to be working in certain ways, but fail to live up to those claims.

What Is a Local Optimum?

This post is primarily about the pernicious and dysfunctional effects of using approaches predicated on local optima. By which I mean, taking a narrow view of (part of) a “system of problems” aka mess.

Many folks seem to believe that improving one part of the whole organisation – e.g. the software development function, or an individual team – will improve the effectiveness of the whole organisation. As Ackoff shows us, this is a fallacy of the first order: it’s the interactions between the parts of the organisation-as-a-whole that dictate the  whole-system performance. In fact, improving any one part in isolation will necessarily detract from the performance of the whole.

This performance-of-the-whole is most often the kind of performance that senior executives and customers (those who who express a preference) seem to care about – very much in contrast to the cares of those tasked with, and rewarded for, improving the performance of a given part.

“When a mess, which is a system of problems, is taken apart, it loses its essential properties and so does each of its parts. The behavior of a mess depends more on how the treatment of its parts interact than how they act independently of each other. A partial solution to a whole system of problems is better than whole solutions of each of its parts taken separately.”

~ Russell. L. Ackoff

Ad-hoc

Also known as code-and-fix, hacking, messing about, and so on. Coders just take a run at a problem, and see what happens. Other skills and activities, such as understanding requirements, architecture, design, UX, testing, transfer into production, etc., if they do happen, happen very informally.

Batch & Queue

Perhaps more widely known as “Waterfall”. In this approach a big batch of work – often a complete set of requirements – passes through various queues, eventually ending up as working software (hopefully), or as software integral to a broader product or service.

Scrum

One of the various flavours of agile development. Other dev-team centric approaches (xp, kanban, scrumban, FDD, etc.) have similar relative effectiveness, whether combined or “pure”.

DevOps

DevOps here refers to the integration of dev teams with ops (operations/production) teams. This joining-up of two traditionally distinct and separate mini-siloes within the larger IT silo gives us a glimpse of the (slight) advantages to effectiveness resulting from taking a slightly bigger-picture view. Bigger that just the dev team, at least.

Lean

Lean Software Development aka Lean Product Development. The (right)shift in effectiveness comes from again taking an even broader view of the work. Broader not only in terms of those involved (from the folks having the original ideas through to the folks using the resulting software /product) but also broader over time. Approaches like TPDS – including SBCE – improve flow and significantly reduce waste by accepting that work happens more or less continuously, over a long period of time, not just in short, isolated things called “projects” nor for one-off things called “products”.

FlowChain

(Including e.g. Prod•gnosis.) My own thought-experiment at what a truly broad, system-wide perspective on software and product development could make possible in terms of improved effectiveness.

Acme

The best possible approach in an ideal world. I’ve included this, somewhat speculatively, as a milestone for just how far we as an industry have yet to go in embracing the advantages of a broad, interaction-of-the-parts perspective, as opposed to our current, widespread obsession with narrow improvements of individual parts of our organisations.

Please do let me know if you’d like me to elaborate any further on any of the above descriptions.

– Bob

Postscript

For some reason which made sense inside my head at the time, I omitted Theory of Constraints from the above chart. For the curious, I’d place it somewhere between Lean and FlowChain.

 

Flow, Shmo

We hear a lot from certain quarters about the benefits of flow – i.e. of value, through eg a value chain, or network, of suppliers to eg customers. I myself have written about it on occasion. And I even had the job title of Head of Product Development Flow, last year.

As a guideline for the initiated, this can work. See: the Lean Decision Filter.

But, as I wrote more recently, the Antimatter Decision Filter illustrates how flow, and even value, comes some way down the list of what matters to most people.

And all this finagling around flow (or value, or even needs, for that matter) is moot to the point of utter batshit irrelevance to most folks out there in businessland and beyond.

So what does matter to people? Don’t ask me. Why not ask them?

– Bob

Further Reading

Theory of Constraints 3 Bottle Demo to improve Flow ~ Youtube video

No More Stupid Punts

What do I mean by “stupid”?

“Mah momma says: ‘Stupid is as stupid does, Forrest'”

~ Forrest Gump

We’re all trying to get our needs met. How we go about that can span the whole spectrum between very smart, and very stupid.

In my vocabulary, “smart” means we’ve chosen, found, or stumbled-upon an effective way of getting our need met, and conversely, “stupid” simply means that we’ve chosen an ineffective way to get our need met.

And boy have I been stupid.

A Series of Stupid Punts

Over the past ten years or so, I’ve taken a series of engagements (jobs, contracts, etc.) in the hope of helping folks – folks who’ve assured me that they wanted help, btw. Generally I’ve directed my help towards improving their company in some way. Sometimes this has been related to an Agile adoption, sometimes to some kind of Lean transformation, and sometimes to improving e.g. software or product development in general.

These engagements have all been punts. That is, the outcomes have been uncertain, and the clients’ commitment to change, although avowed and often emphatic, unproven. Stupid punts.

Ill Met by Moonlight

In all cases – whilst, of course, getting paid for my efforts – I’ve just been trying to help folks. And have been focussed primarily on their needs. And in the process, not paying much attention at all to my own needs. So, unsurprisingly perhaps, my own needs have often been ill met.

My Needs

Here’s a list of the needs I’m talking about:

  • Meaningful connections – the opportunity to make meaningful connections with people. Given that my help is most often directed towards seeing the whole organisation thrive, flourish and become more effective, “meaningful connections” includes everyone in the organisation – from the executives (board, management team), to the frontline folks (devs, ops, sales, marketing, support, etc.).
  • Mutual learning – exploring interesting topics together with other folks , and learning together about things to do with making businesses more effective.
  • Contribution – actually making some appreciable contribution to the improvement of folks’ lives at work, and to the healthy growth and progress of the organisation as a whole, too.
  • A sense of progress – a.k.a. accomplishment. A feeling that folks’ efforts are not wasted, that things are in fact moving – and in the “right” direction.
  • Regard – being “successful” enough that folks would hold my contribution in sufficiently high regard that they would recommend my services to others.
  • Well-being (of self and others) – in particular, helping folks get their needs met, relating to one another humanely, and – for those who wish to – fully realising their innate potential.
  • Mutual joy – in the nonviolent communication sense of the term (through e.g. self-empathy, empathy, and honest expression). See also: Brahmavihara

Aside: The correlation between the above list and Martin Seligman’s idea of P.E.R.M.A. is a happy coincidence, yet unsurprising, I guess.

I wrote a post recently explaining how my then-job was not meeting my needs in that particular position. It may come as no surprise to hear that I resigned shortly afterwards.

Turning Point

To date, I’ve often been so focussed on the needs of others (clients, co-workers, employers) that getting my own needs met has been pretty much squeezed out. This regularly leaves me feeling depressed, angry and, often, alienated.

I’m resolved to find a more balanced position between my needs and those of others. And to begin to work on less stupid ways of getting my own needs met, too.

I’ve reached a point in my life, with the help of Marshall Rosenberg, where getting my needs met seems crucial to my happiness and peace of mind. This has become sufficiently important that I’m resolved to take some steps to significantly increase the likelihood of that happening in future. I am presently thinking on what such steps might look like.

If and when this is working well, I anticipate better outcomes not just for myself, for all. I will still keep taking punts, just not quite such stupid ones. Semper mirabilis, indeed.

Cobblers

In closing, I note a certain irony. For some twenty years now I have taken careful account of the needs of all stakeholders in whatever endeavour I have been involved. Just not, it seems, my own needs. Cobblers’ children, anyone?

– Bob

The Bailer’s Creed

This is my resignation. There are many like it, but this one is mine.

My resignation is my best friend. It is my life. I must master it as I must master my life.

My resignation, without my resolve, is useless. Without my resignation, I am useless. I must fire my resignation true. I must hold to my resolve more than my employer, who is trying to bury me. I must quit him before he buries me. I will…

My resignation and I know that what counts in this life is not the hours we put in, nor the appearance of busyness, nor the bluster we make. We know that it is the joy that counts. We will find joy…

My resignation is human, even as I, because it is my life. Thus, I will regard it as a brother. I will learn its weaknesses, its strength, its paragraphs, its core values, its date and its signature.

I will keep my resignation prepped and ready, even as I am prepped and ready. We will become part of each other. We will…

Before all, I swear this creed. My resignation and I are the defenders of all workers. We are the masters of our employers. We are the saviours of my life.

So be it, until victory is the people’s and there is no enemy, but joy in work and life!

– Bob

Misery Loves Company

If you follow me on Twitter, you may have noticed I’ve been a less than happy bunny of late. I put it down to working for an unreconstructed Analytic-minded organisation.

In this regard, have you come across the “twelve questions” that define a great place to work – according to 25+ years of research by the Gallup polling organisation?

I’ve used these twelve questions with several groups in previous organisations, to get a feel for what’s working and what’s borked, and also to show an interest in people and their well-being.

So, I thought, why not ask myself the same twelve questions today? Having done so, I thought I’d share the results with you. Misery loves company. ;}

It’s not pretty, is it? How would you fare on these twelve questions in your current job, right now?

– Bob

Further reading

First Break All the Rules ~ Marcus Buckingham and Curt Coffman

Null-A

Hands up all those who read or have read science fiction? I was an avid reader of science fiction in my youth, particularly of the “Golden Age” writers, including: Harry Harrison, Norman Spinrad, E.E. “Doc” SmithFrank Herbert, Arthur C. Clarke, Robert A. Heinlein, Michael Moorcock, Isaac Asimov, and above all A.E. van Vogt.

In some strange way, these authors and their works helped me make sense of a chaotic youth, and laid some foundations for my future.

The most enduring of these influences was, and is, A.E. van Vogt and his Null-A series. In these books, van Vogt explores meta-systems, and in particular Alfred Korzybski‘s General Semantics, through the adventures of his aptronymous hero Gilbert Gosseyn.

“…he’s at least as great a man as Einstein. At least – because his field is broader. The same kind of work that Einstein did, the same kind of work, using the same methods; but in a much broader field, much more close to human relationships.”

~ Heinlein on Korzybski

Logics

For me, one of the core differences between, on the one hand Adhoc and Analytic mindsets, and on the other Synergistic and Chaordic mindsets (see: The Marshall Model), is the kind of logic at work (sic). The former seem to use Aristotelian logic exclusively (on those occasions where logic is used at all), whilst the latter appear to favour some form of Non- Aristotelian logic.

What Does it All Mean?

I’m sure I don’t know. But I suspect the inclination of some folks (and by extension, organisations) to think in black-and-white, zeroes-and-ones terms (cf. Aristotle, Newton, Euclid, etc.), and others to (sometimes) think in probabilistic, many-shades-of-grey terms (cf. Leibnitz, Bayes, Keynes, Zadeh, Cox, Prigogine, etc.) has something to do with it (the ‘it’ here being organisational effectiveness).

“Had Aristotle been a bit smarter, we could have saved a few thousand years of muddle by doing logic the proper way from the beginning.”

~ Mike Alder

What do you think?

– Bob

Further Reading

The World of Null-A ~ A.E. van Vogt
The Pawns of Null-A ~ A.E. van Vogt (a.k.a. The Players of Null-A)
Null-A Three ~ A.E. van Vogt
Aristotelian and Non-Aristotelian Logic ~ Gotthard Günther
An Introduction to Non-Aristotelian Systems ~ Ben Hauck
Fuzzy Thinking ~ Bart Kosko
Non-Aristotelian Logic in Practice ~ Mike Alder (Excellent)
Probability Theory: The Logic of Science ~ Ed Jaynes (‘Unfinished’ online version)

Transitioning From Amplify.com Blog

GIven the continuing poor performance of the Amplify.com site, I’ve decided to set up a new blog here on WordPress. Hopefully this will prove less frustrating for all concerned.

Previous posts remain available at my old blog site. (I wonder how much longer Amplify.com will remain a viable service).

– Bob

 

There’s a Lot of it About (Bullshit)

[From the Archive: Originally posted at Amplify.com Jan 20, 2011]

[Update: The original source article is no longer available. This post now links to a Wayback Machine archived copy]

A key observation, and very germane to the worlds of IT, software development, product development and consulting:

Amplifyd from www.regrettheerror.com

Battling Bullshit 

One challenge is that “digital and media literacy” is a very broad area. Allow me to focus one small but essential sliver of the new, urgent literacy: bullshit detection.

Bullshit, you see, is everywhere. It is being produced, perfected, pontificated and pushed out at astounding rates by all manner of people and organizations. It spreads and multiplies. It morphs and mutates. People spew it, broadcast it, print it, tweet it, like it, blog it.

The bad news is there is too much bullshit. The good news — cue the theme to The Six Million Dollar Man — is we have the technology to defeat it. The strange news is that very same technology is also helping spread bullshit. Let me put it this way:

The Internet is the single greatest disseminator of bullshit ever created.

The Internet is also the single greatest destroyer of bullshit.

In between is a confusing world that is far less binary than the above construction. As that Concordia student put it, it’s a world that sometimes seems characterized by “too much.”

Which means all of us need to develop what Ernest Hemingway called a “a built-in bullshit detector.“ Universities need to teach the new literacy, to give people the tools to sniff out bullshit and practice the art of verification.

Read more at www.regrettheerror.com

 – Bob