Tag: ctobook

  • Information for Technologists Interested in Learning about Artificial Intelligence

    Information for Technologists Interested in Learning about Artificial Intelligence

    This article is primarily for people with a background in technology and software engineering wanting to learn about AI. Topics include artificial intelligence, machine learning, deep learning, artificial neural networks, reinforcement learning and more machine learning related concepts. Articles about AI for the General Audience AI In Digital Media, News, and Journalism AI In The…

  • 7 minus 1 reasons why technology/engineering teams should work on projects

    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…

  • CTO Mind Map: Culture, Technology, Operations

    In the role of chief technology officer, you have to be concerned with many topics. Some relate to functions you have direct supervisory responsibility for and some in areas that are managed by others but you still need to share responsibility for. To keep all of a CTO’s concerns organized, I created this mind map using XMind. The items are classified under…

  • Dear Makers, On Fridays My Office is Yours — An Experiment

    Dear Makers, On Fridays My Office is Yours — An Experiment

    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…

  • 3 Dimensions of a Technology Team

    Organizing Software Engineering Teams to Balance Products, Partners & Professions This organizational design for a technology department aims to optimally blend the need for the technology team to be an engine of innovation, a customer-service organization and technically excellent. It views the staff, roles and responsibilities in three dimensions: products, partnerships, and professions. Organization by…

  • 3 Roles of a CTO: Culture. Technology. Operations.

    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…

  • 3-5-7 Meeting Format for Weekly Staff Meetings

    If you are the manager of a team of people at your job, here is a format we suggest for running your staff meetings. We call it the 3-5-7 format because of its convention of giving 3 to 5 minutes per person to answer 7 questions. This system assumes that you have fewer than ten direct…

  • Posted Signs for Productive Meetings

    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.

  • Suggested Template For Requesting a Meeting

    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…

  • Templates for Replying to Meeting Requests & Polite Ways to Decline Meetings

    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…

  • When to have and when not to schedule 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…

  • 50/25 Meeting Format

    Update (2023 September 17): I published an update to this system based on data, experience, and the advice of colleagues. If you manage a team, value your team members time and want to improve productivity at your workplace with a simple change, consider implementing the 50/25 Meeting Recommendation that some companies are embracing. Consider communicating…