06Jun

You’ve just been tapped to lead a development team on a new project. It’s a sign of the company’s confidence in you and the opportunity you’ve been wanting for a while.

Now that you’re back at a workstation, reality is setting in. What do you need to get your team on board and rowing together?

In a word, it’s leadership. And that has far less to do with your coding skills than your ability to communicate, motivate and collaborate. Your team will look to you for guidance in setting priorities, advocating for them up the food chain, and working with them to solve problems.

“In today’s world,” says The Ohio State Engineer Magazine, “It is essential for an engineer to possess strong communication skills; it is the biggest determiner of success in the modern engineer’s professional career.” This goes double for project leads and managers.

Clear communication starts with knowing the details of the project, defining the end goals clearly, assigning roles and setting expectations. Clarity is essential, so even when you see nodding heads, don’t assume everyone understands. Ask for discussion. A diplomatic way of ensuring your team understands what needs to be done is ask if the process and goals are realistic; does anyone see any potential problems. Invite pushback on the timeline.

Besides uncovering misunderstandings or communication gaps, you’ll demonstrate your openness to disagreement and differing points of view. Creating an environment of psychological safety is the single most important component of team success, according to Google, which exhaustively studied team leadership.

Slack blog post describes how a team lead creates psychological safety:

  1. An empathetic approach – “Strive to read your teammates. Are they content, stressed out or struggling?… Aiming to empathize with their point of view is key to gaining their trust.”
  2. Practice active listening – This means listening to understand what the person is saying rather than thinking of how we will respond.
  3. Avoid finger pointing – Constructive feedback is helpful. But blaming does nothing good. When problems arise — and they always do — focus on how to solve them. Involving the team in finding solutions is often a smart way to find creative ways to resolve problems.
  4. Be humble – When you make a mistake, admit it. When you’ve been short with someone, apologize. Say “please” and “thank you” often.

Image by Free-Photos from Pixabay

[bdp_post_carousel]

CIO or CTO? Does it Matter?

What’s the difference between a CTO and a CIO?

“Good question,” admits ZDNet. Where once the Chief Information Officer was universally acknowledged as the most senior IT executive, now, says the tech site, it “depends very much on the type of business you’re talking about.”

Where a business has only a CIO or a Chief Technical Officer, it’s an easy call – that’s the top IT executive. The duties and responsibilities are clear. Where the situation gets murky is when an organization has both.

Explains ZDNet, “The traditional split is that the CTO is responsible for the operational concerns associated with technology implementation. CTOs drill down into the details of technology. They have a strong systems focus and they know how technology works, making it more of a chief architect role.

“CIOs, on the other hand, tend to focus more on engaging with the business. So while the CTO might go and speak with vendors to source technology, the CIO makes sure the internal business gets the secure and governable systems and services it wants.”

Everyone got that? No? How about this from InsiderPro:

“CTOs are similar to CIOs. But they are responsible for the overarching technology strategy and infrastructure to help meet the organization’s goals, while CIOs oversee the IT departments and staff to manage everyday operations and in many cases work with business leaders on aligning IT with business goals.”

Where both roles exist, InsiderPro says “the CTO usually reports directly to the CIO.”

But wait. Pointing out that “As the importance of technology within the business has risen, so has the demand for knowledgeable technologists,” ZDNet says, “Some businesses – including established enterprises – have opted to rely more on a CTO than a CIO.”

Dig a little further and you’ll find that the hierarchical distinction is becoming less important as the bigger businesses move ever further along the path to digital transformation. Bornfight, a project-focused development firm, has a different take on the relationship between chief technology and chief information officers. It defines the jobs this way:

  • “Chief Information Officers are members of the executive team who are responsible for ensuring that a company leverages technology in a way that helps it optimize, improve and streamline internal processes.”
  • “Chief Technology Officers are members of the executive team who are responsible for ensuring that a company’s product utilizes technology in a way that will meet the customers’ needs.”
  • The company included this handy chart comparing the roles.CTO vs. CIO - blog.jpg

Bornfight’s most significant contribution to the discussion may well be that in organizations large enough to need both, CIOs and CTOs are complementary to each other.

“From a business perspective, you need these two positions and you need them to fit well together and cooperate — this leads to progress. The right way to approach this is to look at these positions as two sides of the same technology coin, a sort of a buddy-buddy relationship.”   

Photo by ThisisEngineering RAEng on Unsplash

[bdp_post_carousel]

Green Key Unlocked: The Effect of Tech Layoffs

Companies such as Microsoft and Google have cut thousands of positions in the last few months. In an effort to prepare for a darker economy, there are new layoff announcements emerging from Big Tech every day.