Checklist for status summaries
Aug. 18th, 2004 02:00 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
I then created a slide called “plans for next quarter” and repeated the process, first listing the projects that were on my agenda and then making sure that each person on the leadership team could point at one of them and say, “ah, he’s keeping my requests in mind.”
For each item I asked myself, “Who would sponsor this item?” That helped me figure out how to rephrase some of the items more succinctly. I could focus better since I was thinking, “How would I explain this to the sponsor” or “how did the sponsor request that item?” A very long description of LAN problems in a certain building was shortened to be “Fix {the issue as the sponsor described}”, which will be much more understandable than trying to explain about Ethernet topology issues and their effect on reliability.
I have a difficult time removing things from a list to make it shorter, and these lists were growing a little larger than one should put on a powerpoint slide. It dawned on me that if I can’t decide what to remove, I could check to see which items had no sponsors. It’s interesting to point out that I never actually removed any items. Rephrasing things more succinctly saving enough room that I didn’t have to.
no subject
Date: 2004-08-18 06:04 pm (UTC)Why don't more technical people think like this? I only hope I remember to keep your strategy/method in mind in case I ever wind up in another tech job again in my life. (Unlikely, I know. Heh.)
no subject
Date: 2004-08-18 10:42 pm (UTC)no subject
Date: 2004-08-19 02:41 am (UTC)I'll be in the area Aug 19-23 if you wanna hang out.
Tom