I saw a tweet from Bill Owen containing a link to The Email Charter.  The charter has 10 rules to “reverse the email spiral”.  This is really great stuff and we need to get the word out.   I wrote a post titled Focus on Your Commitments – A New Way to Work which explains a way to use your Outlook email client as a productivity tool.  By combining the 10 rules from the Email Charter with the techniques I presented in my blog post, I expect to save even more time.

Here are the 10 Rules

  1. Respect Recipients’ Time
  2. Short or Slow is not Rude
  3. Celebrate Clarity
  4. Quash Open-Ended Questions
  5. Slash Surplus cc’s
  6. Tighten the Thread
  7. Attack Attachments
  8. Give These Gifts : EOM, NNTR
  9. Cut Contentless Responses
  10. Disconnect

Take a look, start using the rules and spread the word!

 

I wrote a post titled How Would You Reorganize an Application Service Delivery Model? in March 2010 and thought it was time to update you on the changes we made to our Application team.

At that time, my team was structured by role:  DBAs, Developers, Application Administrators, Email Administrators, etc.  Over that time, we had some successes with the structure and some challenges.

Some challenges with the role based structure included:

  • separation of developers and DBAs – resulted in delays, rework when developers did not meet coding standards expected by DBAs, and disconnected teams
  • separation of services that had tight integration like our portal environment from the ERP platform
  • mixture of platform skills that caused service support issues when service recovery work crossed team boundaries
  • challenges in providing minimum staffing coverage and training when support spanned team boundaries such as Identity Management, Project Management and Business Analysis work

In September 2010, we had an opportunity to reorganize our team.  After consulting with our team members and team leaders, we changed the structure to suit the two main architectures that our team supports – Microsoft and Oracle.  Essentially, we moved the developers to the platforms they predominately worked in and realigned the services that required tight integration.

Comparison of Role Based Structure to Platform Based Structure for Application Services

Role Based Structure Platform Based Structure
Support Team Oracle DBA Oracle Team Oracle DBA
Document Management Business Intelligence
Business Intelligence Document Management
Project Management Enterprise Portal
Business Analysis ERP Administration
Identity Management Java/Web Services Developers
Oracle Developers
Email and Collaboration Team Email Administration Identity Management
Calendaring Business Analysis
Instant Messaging Project Management
Collaboration Platforms Microsoft Team
SQL Server DBA Email Administration
Microsoft Applications Calendaring
Enterprise Portal Instant Messaging
Collaboration Platforms
Developer Team Java/Web Services Developers SQL Server DBA
Microsoft Developers Lotus Domino Developers
Oracle Developers Microsoft Applications
Microsoft Developers
Identity Management
Business Analysis
Project Management

We have been running with the structure for almost a year now and are seeing the benefits of aligning our Application Services team with our main support platforms.  I will revisit this structure annually to ensure that our team is organized to best serve our client community.

 

Do you start the day opening your email and looking at the hundreds or thousands of messages in your Inbox?  How does that make you feel? Overwhelmed, stressed and feeling like you are always behind on your commitments?

Do you have days where you know you worked very hard but somehow have nothing to show what you accomplished?  How does that make you feel? Unproductive, overworked and stressed?

Do you feel that everyday you are at the beck and call of everyone else and do not have any control of what new crisis will hit you next? How does that make you feel?  Dis-empowered, helpless and always wondering what the next crisis is?

These three symptoms typified my work life since I became a manager almost four years ago.  I often said to my fellow managers:

“I am working really hard but it is not sustainable to do 10 and 12 hour days.  I have to find a way to work smart so that my hard work really pays off!”

I attended a training course on using Outlook 2010 in May that has fundamentally changed how I approach my work.  The course was offered by Priority Management Systems Inc and called Working Sm@rt with Microsoft Outlook.   The course focused on using Outlook as a real productivity tool instead of using it just for email and calendaring. The instructor calls this “using Outlook with a business planning approach”.

The premise of the course is that in order to be productive, you need to focus on your commitments.  To do this, you have to stop using your email Inbox as your To Do list.  Face it, who puts things in your Inbox?  You or other people.

As long as you start your day working in your Inbox, you will always be reactive in your efforts and working to someone else’s agenda.

To change this approach, the instructor helped us configure out Outlook client to open in our calendar and task list view.  This is revolutionary for me.  Previous to this, I used my Inbox, a paper based Day Timer journal, a Notepad document, a OneNote page and an Excel spreadsheet to try to keep To Do lists.  None actually suited how I worked and I always found that I missed something or got distracted by conflicting priorities due to using multiple lists.

© 2007-2012 Enterprise Architecture in Higher Education - Leo de Sousa Creative Commons License
Enterprise Architecture in Higher Education by Leo de Sousa is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License.
Based on a work at leodesousa.ca.
Suffusion theme by Sayontan Sinha

Switch to our mobile site