[41] in iswork
Results of "change" brainstorming on 4/6/00
daemon@ATHENA.MIT.EDU (Tim McGovern)
Tue Apr 11 10:55:41 2000
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <v04020a04b518e9839638@[18.152.1.21]>
Date: Tue, 11 Apr 2000 10:55:36 -0400
To: iswork@MIT.EDU
From: Tim McGovern <tjm@MIT.EDU>
Cc: dania@MIT.EDU
The question we tackled was:
what specific business practices does IS need to adopt
to increase the likelihood of success for this project?
With minimal editing, here's what we came up with:
1. Motivate ITLT to use the repository.
2. Document standing team work.
3. End idiosyncratic priority setting.
4. Communicate the politics of some projects.
5. Provide periodic review of some projects.
6. Communicate why some projects are higher priority.
7. Don't reward non-participants.
8. Allow for fast-breaking priorities.
9. Foster more public visibility for all kinds of work.
10. Don't rely solely on the passive repository of data about work.
11. Use post-mortems for all efforts -- good and bad.
12. Develop a system of reminders when information is incomplete,
or possibly stale (how often, how, and to whom were
unresolved).
13. Determine a reasonable standard for responding to work proposals.
14. Benchmark how IS gets work done today.
15. In one year, measure again to see if we are getting better.
16. Get everyone in IS to know what the ISWork repository is.
16. Develop clear guidelines for when, whether and how to involve ITLT
in all kinds of work.
The next logical step for this part of the project is to meet with Dani and
our sponsors and begin mapping out the business change strategy. I have
the action item to set up that meeting.
Tim
