Management Bits and Tips

From time to time it is useful to have formal thank-you-for-your-service letters emphasizing how customers need your services for day-to-day running of their business processes and / or during their critical situations (bit). Have ready templates for asking about such letters (tip).

Follow-through prioritized service requests with feedback templates. If there are no critical issues schedule periodical questionnaires. When people ask you for a service-favour request a letter clarifying how your service-favour reply helped them to do their business.

- Dmitry Vostokov @ ManagementBits.com -

To look at your salary expectations from a new angle I recommend at least to read the description of the following book that I “wrote” and published:

Salary Figures: A Codebook of Expectations

- Dmitry Vostokov @ ManagementBits.com -

A book can serve the role of CV but a CV can serve the role of a book. Elaborating on this idea I decided to publish my old CV (1987 - 2003) as a book and as an example of a person with CV-writing obsession like I had 5 - 8 years ago. Book details can be found here:

Forthcoming CV as a Book

Front cover of my CV

- Dmitry Vostokov @ ManagementBits.com -

To my shame I have never read the famous book “AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis”. Being interested in antipatterns which I often figure out myself in the practical domain of software technical support (see Crash Dump Analysis AntiPatterns) I looked for the most recent collection of the management ones and found this book which I’m reading now:

Antipatterns: Identification, Refactoring, and Management (Auerbach Series on Applied Software Engineering)

In addition to their own patterns, the authors of the book provide the description of Brown’s antipatterns (the book mentioned earlier, “AntiPatterns: Refactoring Software, …”), provide two tables for easy antipattern identification in an organization or a team (Management Antipattern Locator and Environmental Antipattern Locator), list and comment on Myers-Briggs personality types, discuss Keirsey temperament groupings and Bramson’s human personality phenotypes. Highly recommended. I especially liked “All You Have Is a Hammer” antipattern of which I was guilty myself during my earlier Team Lead role experience.

- Dmitry Vostokov @ ManagementBits.com -

Some people don’t feel good when they see themselves second or last on To: and Cc: email recipient lists or any other list that lists them (bit). Alphabetize the list and even mention casually that you do so (tip).

Prioritize, Alphabetize, Perspectiwise

The second P is not a misprint but the summary that puts the alphabetization of To: and Cc: lists into perspective wisely!

- Dmitry Vostokov @ ManagementBits.com -

Have you ever seen or worked with a person that never provides concrete answers or in the worst case doesn’t answer at all? Perhaps this persons considers any question as rhetorical and therefore has RQD. You need to stop asking questions and make statements instead.

- Dmitry Vostokov @ ManagementBits.com -

The pressure to deliver is great nowadays (bit). Utilize time-proven software engineering techniques like reuse of accomplishments and artifacts (tip).

Classical example of this is called WORM: write once, report many. For example,  you write an article once and report the number of views every month. Of course, the article needs to be popular enough to report.  

- Dmitry Vostokov @ ManagementBits.com -

I found this book in a local bookshop a few months ago and now I recommend it to everyone dealing with customers, either internal or external:

Managing Expectations: Working with People Who Want More, Better, Faster, Sooner, NOW!

Foreword was written by Gerald Weinberg.

- Dmitry Vostokov @ ManagementBits.com -

Although I still use Preemptive Multireading throughout my working day I decided to try another approach similar to cooperative multitasking used in old operating systems like Windows 3.x. I identified 30 technical books I want to read (mostly related to software engineering, software architecture, design and programming) and allocated one hour every day to spend about 2 minutes on each book. Most software related books have low information density per page and plenty of information is repeated from book to book which allows using some speed reading techniques. These books are unlike mathematics, physics and computer science books where I have to meditate on proofs, formulae and examples. So I switch to another book every 2 minutes and do this 30 times. 2 minutes is usually sufficient to read and turn a page and these amounts to 60 pages per day (one page per minute). An average 300-page book can be finished in 7-8 months and therefore I can read at least 30 books per year using this approach, read all of them together and don’t wait for a second book until I finish the first one! The last point is psychologically very important to me because I want everything now

A technical note: it might look that we still use preemptive multitasking with a fixed quantum here but in reality there are no external interrupt sources. All I do is to voluntarily yield reading control from one book to another. I can always spend one or two minutes more with a book if its current chapter is very interesting.

- Dmitry Vostokov @ ManagementBits.com -

Thick books impress people (bit). Write and publish a technical book related to your work to show the complexity and importance of what your team does and highlight the technical ability of your department (tip).

If there is a perception among other people that the job of your team is easy and tasks can be accomplished more quickly then sufficiently thick book shows the opposite and emphasizes quality vs. speed.

- Dmitry Vostokov @ ManagementBits.com -