Tuesday, 6 December 2011

Atom 3: Do we need to look at Deliverables as part of process?

User Experience and the IT realm look at the term "Deliverables" as a strict driving model. Deliverables are a line of division that the Client and Service company embark on to find solutions. Deliverables are also seen as a measure to an individual in assessing the work nature, whereas the Client looks as a bunch of "hardcore" documents, artifacts & systems that needs to be in place that is driven by a schedule. This no more creates fun when something is hardwired. Just imagine if your liberty is taken off, by keeping constant cameras to watch your   steps. How it tames your self and individual freedom ? How it keeps you to know that being monitored ? Such is the term deliverables really looks a "death-word".

When work needs to be fun and people wanted to clearly cross the line, there should be systems that are atleast hidden or sugar-coated. Atleast sugar-coated for the sake of creating a habitual ease at work. There is nothing wrong when Deliverables are segregated to evaluate and look at progression goals. But lets comprehend if the world would have tweaked the term into "Engagement Model".

Engagement Model will still have goals and so called "deliverables" intact, but it would never be deemed to create illusionary paralysis on any individual. Engagement model precisely is elastic and rids away the definitive clauses of deliverables. If you were to engage the client, the client would definitely be glad ! To create such an engagement what kind of processess would an individual follow ? What kind of actions does one represent to create an engaging work ? How will one engage with ease and create wow factor ?

I hate the terminology of deliverables to ruin the work-place and create an imaginary division between two parties. If it were to say, What kind of Engagement Model one proposes with clear pointers or "Actions" is a fluidic approach with boundaries to contain that it never spills-out. Perceptions change when "Engagement Model" as a term that also brings in a more collaborative approach rather driven into self-enclosures of "deliverables".

No comments:

Post a Comment