Background I care deeply about the people in my life. I value my relationships with them. I cherish in-person, face-to-face conversations. In my personal and professional life, I rely on video conferences, email, and instant messaging. In some cases, I might communicate with you frequently, in others once in a while. Like it is for… Continue reading Why I Recommend Using Spike for Email, Instant Messaging, and Video Chat (Review)
This is a framework for understanding, describing, and performing your job duties, roles, and responsibilities. You can use this as a template to create a useful job description that you would actually use while you are in a job. It divides a job into three categories: activities, outputs, and outcomes. To be successful in your… Continue reading Activities, Outputs, and Outcomes — A framework for your job
Here is an example of how to respectfully decline a meeting to make time to work on a higher priority. We occasionally find ourselves in meetings when our time could be better spent doing something else of greater value. I previously wrote about how to respond to and politely decline meeting invitations. This post is about… Continue reading An Example of Respectfully Declining a Meeting at Work That is Already in Your Calendar
Here are 6 reasons that should be used to justify, prioritize and classify projects engineering teams work on. The 7th item is not a valid reason to be used. Deliver products, features and services as driven by business priorities (#product) Improve time to market (#speed) Improve quality of experience (#quality) Improve efficiencies and reduce costs… Continue reading 7 minus 1 reasons why technology/engineering teams should work on projects
Some senior leaders choose to work alongside their teams in cubicles, eschewing private office rooms. New York City’s former mayor Michael Bloomberg is an example. Facebook’s founder and CEO Mark Zuckerberg is another. Intel’s former CEO Andy Grove is often credited for setting this example. As I’ve worked at various news media companies, I have… Continue reading Dear Makers, On Fridays My Office is Yours — An Experiment
This is a guide for CTOs, VPs of Software Engineering and other technology managers responsible for a software engineering organization. The purpose of this checklist is to help the CTO cover the areas of culture, technology and operations in their teams. It is presented in the form of a memo to direct reports. Dear Tech… Continue reading 3 Roles of a CTO: Culture. Technology. Operations.
You can post these slides as signs in your meeting rooms and offices or include them at the start of your presentations. You can also open the original Google Slides document to print or leave comments.
Every time someone calls a meeting, they should consider using this simple template. [ meeting-invitation-template begins ] The desired outcome of this meeting is: e.g. Come to agreement on solution for issue X e.g. Make a decision about Y. e.g. Share announcements about topic Z. e.g. Continue to grow a good working relationship with each… Continue reading Suggested Template For Requesting a Meeting
By default, we should only attend meetings where we are active participants, not passive attendees with not much to contribute to the desired outcome of the meeting. There are some exceptions to this like training sessions, educational presentations or others where the purpose for attendees is to learn something. When I receive a meeting request, I… Continue reading Templates for Replying to Meeting Requests & Polite Ways to Decline Meetings
Companies should, by default, avoid scheduling meetings that start before 10am or end after 5pm. If an employee comes to the office at 8am on some days, it is often to use the two hours of the morning before meetings to catch up and/or get a head start on the day. Meetings that start before… Continue reading When to have and when not to schedule meetings