Process

Posted by Kirsten Gibbs on January 30, 2019
  • What springs to mind when I use the word ‘process’ in conversation with people is something boring and robotic – a highly detailed description of how to perform some low-level, small-grained task, devoid of context and utterly lacking in colour and humanity.

    I think that’s because the most commonly used languages for describing processes comes from the automation space. These processes are instructing machines, not humans. Every alternative scenario has to be exhaustively described and programmed for, every detail has to be spelt out – because machines are literal, they do exactly what they are told, no more, no less.

    Professionals aren’t machines. You can leave them to fill in gaps, interpret things in their own way, devise better ways of getting to the desired outcome. But they do appreciate some process – as a route map to follow, a checklist to ensure nothing important is forgotten, as a pattern that saves them from re-inventing the wheel every time.

    That’s why we have musical scores; screenplays and storyboards; choreography and librettos; game plans and recipes. We’re quite happy to be told what to do, as long as it is at the right level with enough wiggle-room to make it our own.

    I believe we need the equivalent for business – so that wherever professionals get together to make and deliver promises to clients they can easily master the core of the process, then clear their heads and hearts for the difficult, interesting, stretching work of interpretation and delivery.

    Adopting the language of machines isn’t the answer.

array(5) { [0]=> object(WP_Term)#1271 (10) { ["term_id"]=> int(30) ["name"]=> string(10) "Delegation" ["slug"]=> string(10) "delegation" ["term_group"]=> int(0) ["term_taxonomy_id"]=> int(30) ["taxonomy"]=> string(8) "category" ["description"]=> string(0) "" ["parent"]=> int(28) ["count"]=> int(19) ["filter"]=> string(3) "raw" } [1]=> object(WP_Term)#1272 (10) { ["term_id"]=> int(1) ["name"]=> string(32) "Discipline makes Daring possible" ["slug"]=> string(32) "discipline-makes-daring-possible" ["term_group"]=> int(0) ["term_taxonomy_id"]=> int(1) ["taxonomy"]=> string(8) "category" ["description"]=> string(0) "" ["parent"]=> int(0) ["count"]=> int(225) ["filter"]=> string(3) "raw" } [2]=> object(WP_Term)#1273 (10) { ["term_id"]=> int(41) ["name"]=> string(18) "Enabling Framework" ["slug"]=> string(18) "enabling-framework" ["term_group"]=> int(0) ["term_taxonomy_id"]=> int(41) ["taxonomy"]=> string(8) "category" ["description"]=> string(0) "" ["parent"]=> int(28) ["count"]=> int(38) ["filter"]=> string(3) "raw" } [3]=> object(WP_Term)#1274 (10) { ["term_id"]=> int(28) ["name"]=> string(20) "Responsible Autonomy" ["slug"]=> string(20) "responsible-autonomy" ["term_group"]=> int(0) ["term_taxonomy_id"]=> int(28) ["taxonomy"]=> string(8) "category" ["description"]=> string(0) "" ["parent"]=> int(0) ["count"]=> int(111) ["filter"]=> string(3) "raw" } [4]=> object(WP_Term)#1275 (10) { ["term_id"]=> int(50) ["name"]=> string(25) "The Autonomous Enterprise" ["slug"]=> string(25) "the-autonomous-enterprise" ["term_group"]=> int(0) ["term_taxonomy_id"]=> int(50) ["taxonomy"]=> string(8) "category" ["description"]=> string(0) "" ["parent"]=> int(1) ["count"]=> int(93) ["filter"]=> string(3) "raw" } }
Join our Blog
  • This field is for validation purposes and should be left unchanged.