Nathan @ e-gineer: Clarify. Simplify. Implement. - The Diigo Meta page

• 27 Nov 09
  

  Łukasz Piestrzeniewicz

  principles methodology programming usability goals rules @implement

• 25 Nov 09
  

  imported technology project process usability principles methodology implementation

• 24 Aug 08
  

  Robyn Jay

  ebusiness

• 20 Jun 08
  

  Alain Antone

  e-gineer project management

  • Clarify. Simplify. Implement.
  • Design reviews: Brutal refinement and pixel-perfect goodness

  • Zero training

    Every user is time poor. They have no interest or time for attending training sessions. Training is the first and biggest hurdle to adoption of your new system and process. While complexity exists and training is required, users can always reject or work around the process with a politically acceptable excuse - "It's too hard".

    Our aim, through simplification, is to make people's life easier, reduce the burden on their time and remove all the excuses. The reward is adoption, engagement and relief that that finally it's been done the way everyone always thought (individually) it should be.
  • Staying simple

  • Clear, simple solutions challenge traditional project economics

    With a robust process of clarification and simplication, two things happen:

    1. The implementation phase is much easier. (e.g. multi-step, parallel workflow problems become one level approval).
    2. The solution becomes very agile and iterative, since it's only through the project process that new clarifications and simplifications become apparent.

  • Project economics and style change to become:

    1. Focused on user experience. All projects and features must provide a significant improvement to the user experience or process. If the cost of implementation outweighs that improvement, then keep looking for a simpler approach that is not so expensive to produce.
    2. Just in time development and design. Accept that clarity and simplicity are a journey, no one has the vision to see that far in advance. Be disciplined enough to realise that sometimes small feature additions need large architectural change just to keep the overall application as simple and consistent as possible.
    3. Optimised for lifetime value. The cost of an application must include the cost to end users of training, inconvenience and usage. For example, the cost of implementing single sign on must be compared to the cost of X users performing Y logins over Z years.
  • As Mark Twain once wrote "I didn't have time to write a short letter, so I wrote a long one instead".

  5 more annotations...

• 08 Mar 08
  

  Dwayne Harapnuik

  it methodology simplify clarify implement

• 27 Feb 08
  

  gsiemens

  ideas

Would you like to comment?

Join Diigo for a free account, or sign in if you are already a member.