Managing a Micromanager

As you progress in your journey as a tech exec, you will encounter a diverse range of individuals and interact with various personalities. Amongst them, the most vexing leader to work with is undoubtedly the micromanager. Learning how to manage a micromanager can make your life much easier.

This person needs to be in control and wants to know everything you are doing. This is painful because you really need to be on your toes. There is a lot of extra work with a leader who is a micromanager because they constantly want to know what you are working on and want to provide lots of input.

Managing the micromanager

If you’re new and unfamiliar to the micromanager, it takes time to establish comfort. Follow their instructions, stay patient, and they’ll value your ability to comply. Eventually, most micromanagers become more lenient, but trust takes time. The trick is to gain trust swiftly. Here’s what you can do:

  • Regular updates – frequent status reports will help your manager feel good about your activities.

  • Face to face meetings – the more your manager sees you, the more comfortable they are that you are focusing on work.

  • Frank conversations – Although this might be uncomfortable, talk to your manager about giving you more space. Explain that you feel good about where you are with your work, and that you feel like you can be independent.

Micromanagers often display signs of insecurity and tend to have nervous personalities. Building a connection and understanding their interests can help foster a positive relationship. Take advantage of opportunities to discuss topics like family, activities, and sports to create common ground.

Building a connection based on shared experiences, such as attending the same university, can help foster a sense of comfort and trust. This, in turn, allows for more flexibility and understanding in your interactions. However, it’s important to remember that cultivating such connections requires patience and investment of time.

Patience is tough

Your manager may frustrate you, but patience and controlling your temper is key. Showing anger or impatience with a micromanager won’t help. Consistently updating your manager and demonstrating success will eventually lead to the freedom you desire. Stay guarded until your manager becomes comfortable with you.

In summary, remain composed, even in situations where your manager scrutinizes your work, seemingly due to a lack of trust. It’s not solely about trust, but rather a matter of control. Dealing with such personalities can be challenging, but rest assured, you will gain valuable insights from these experiences.

Click here for a post on how a tech exec matches personalities to relate to their counterpart.

Transitioning Projects Offshore

As a technology executive, it’s crucial to manage projects efficiently and cost-effectively. When transitioning projects offshore, integrate them into your overall operational technology model instead of replacing onsite staff. This strategy fosters smoother acceptance and allows the offshore team to seamlessly integrate into your organization, enabling the addition of offshore resources as needed.

India, Mexico, South America, and the Philippines have become key destinations for project staffing. While managing projects across various locations is inherently challenging, relying on offshore third-party teams adds an extra layer of complexity. In this section, we will discuss some of the unique challenges faced when managing projects in these locations and how to address them.

Challenges in Managing Projects Across Multiple Locations

Managing projects across multiple locations can be a daunting task for even the most experienced project managers. From communication barriers to cultural differences, there are various challenges that need to be addressed to ensure successful project management. And when it comes to managing projects in offshore locations like India, Mexico, South America, and the Philippines, these challenges become more complex.

Let’s take a closer look at some of the key challenges faced by project managers when managing projects in these countries:

Communication Barriers

One of the biggest hurdles faced while working with offshore teams is the communication barrier. Differences in time zones, language barriers, and cultural differences can lead to misunderstandings and delays in project progress. To overcome this challenge, it’s crucial to establish clear and effective communication channels from the very beginning of the project. This can include using common project management tools for documentation and tracking progress, conducting regular meetings with all stakeholders, and setting expectations for response times.

Cultural Differences

Each country has its own unique culture, customs, and work practices that can significantly impact project management. For instance, countries like India and Mexico have a more hierarchical business structure where decisions are made at the top level. On the other hand, countries like South America and the Philippines value collaboration and teamwork. It’s essential for project managers to understand these cultural differences and adapt their management approach accordingly.

Technology and Infrastructure Limitations

Project managers may also face challenges when it comes to technology and infrastructure limitations in offshore locations. In countries like India, Philippines, and South America, access to reliable internet connection and updated software can be limited. This can lead to delays in project progress and hinder communication between team members. To mitigate this challenge, it’s important for project managers to plan ahead and provide necessary resources or workarounds for team members.

Legal and Regulatory Compliance

Different countries have different legal and regulatory requirements that need to be followed while managing projects. Project managers need to be aware of these regulations and ensure that all project activities are in compliance with them. This can include data privacy laws, employment laws, and tax regulations. Ignoring these requirements can lead to legal issues and jeopardize the success of the project.

Third Parties

When collaborating with a third party, it’s crucial to embrace their established processes. You chose this organization for their expertise, not just cost savings. Offshore development organizations exhibit remarkable efficiency by refining their processes. Unpleasant encounters often arise from misunderstandings or resistance. Successful collaboration with a third party requires understanding their methods and reaching agreements to integrate work harmoniously. Remember, no two organizations are identical.

It is crucial to have a proficient project manager working onsite in collaboration with an equally adept manager offsite who comprehends the dynamics of both realms. This synergy ensures a seamless workflow and maximizes efficiency.

To foster collaboration and streamline issue resolution, it’s crucial for external individuals to grasp the organizational structure of the hiring company. In a typical setup, an on-site Program Manager interfaces with the Business Unit. For larger programs, the Program Manager’s team includes multiple product managers leading project teams. These teams consist of a project manager, as well as professionals responsible for business analysis, development, testing, and deployment.

The Program Manager works with the project managers to delineate the work to be sent offshore.

Offshore Success

To make the move to an offshore team happen successfully there are a number of activities that need to be completed for the smooth transition of project work:

  1. Establish a PMO offshore to manage building the new operation.  If you are leveraging an offshore provider, they will provide the project infrastructure to support the transition. Leverage the PMO to help coordinate on-boarding activities to fill in leadership gaps until all leaders are in place.

  2. Perform a one-to-one mapping of skills to those being hired offshore in order to understand the level of skills transfer/ shadowing required.  Keep in mind that just replacing staff, one to one based on a schedule, is not a transition plan.

  3. Assign onsite leadership to work with PMO and take ownership of transition.

  4. Identify and/ or hire the management team offshore who will replace or supplement and interface with the management team onsite.  Keep in mind that the offshore team will now “own” the resources.   

  5. Identify the project ordering (what projects are going) for transition, starting with less complex efforts in order to demonstrate success, hone the transition process, and allow the base team offshore to become established.

  6. Build the transition plan to include BU and Program leadership who will assist in the training of new staff.  This will help smooth the transition as leadership will become comfortable that domain and business knowledge is being retained.

Since the new offshore team members haven’t collaborated before (unless through a third party), they will initially lack a sense of cohesion.

Without bonding and unfamiliarity between offshore, onsite, and new recruits, achieving project continuity during site transitions can be challenging. This is particularly true if the onsite team is unaware of the cultural working norms in the offshore location.

Add to the concern that these recruits are unfamiliar with your company’s processes and tools. This puts pressure on the offshore leadership team to establish expectations, scope, and roles for the new hires. The onshore leadership team must also actively assist in training and orienting the new offshore team.

Click here for a post on handling cultural issues in offshore projects.

Tech Strategy Interview Questions

We’ve been discussing the development of a technology strategy. A crucial step in this process is for the tech executive to conduct a tech strategy interview with other leaders, gathering their insights to ensure everyone feels included and has contributed to the strategy.

A strategy without consensus typically falls apart.

Some of the questions that you’ll want to include in the interviews are:

General Questions

  • Can you provide a snapshot overview of your group, i.e., size, business focus areas?

  • What are your organizations priorities/ the strategic objectives?

  • Is your group a strong consumer of technology?

  • If yes, what applications do you use on a regular basis? Are there external applications that you use?

Tech Strategy Environment Questions

  • Today, do you feel that technology is supporting your business strategy?

  • If not, what do you see are the current issues?

  • What would you like to see for future technology initiatives?

  • Are there areas where you feel automation could help reduce cost or increase productivity?

  • What do you consider the highest value systems today? Which have the highest risk – client, regulatory or brand issues?

  • Do you know who to communicate with for IT issues? Who is your contact?

  • In your area, are there regulatory and legal other legal obligations that IT must be aware of? How are these obligations communicated?

  • Do you feel that there is a good level of customer satisfaction related to IT and IT systems?

IT Operations Management

  • Do you feel the IT systems that you use are stable and perform well?

  • Do you feel that the IT systems you use are high quality? What can be improved?

IT Innovation Management

  • Is there confidence within the business towards IT and the services provided?

  • Do you feel IT today provides a process and mechanism to improve or transform the business? Do you feel it could in the future?

  • Is IT today viewed as a “Business Partner”? What is the perception of the IT team?

  • Do you feel IT is supporting/ understands new and strategic business opportunities? How are business opportunities communicated to IT?

Tech Strategy Closing Questions

  • This project is critical to helping build a solid and integrated set of initiatives for supporting business growth. What areas do you feel need attention or could really add value, from your perspective?

  • Anyone else who you feel we should contact to discuss IT systems and/or strategy?

  • Do you have any additional thoughts? May we contact you again if we need to follow-up details?

The tech strategy interview is an important step in the strategy build process. Use this interview framework as a starting point. The best interview is freeform, comfortable, and covers the mentioned key areas. As an executive, asking strong questions for a deeper technology needs assessment is critical. Share findings with interviewees after completing the process. Ensuring understanding and agreement is important for strategy success.

Recovering from a Screw Up

Today was particularly challenging. You made a screw up, and the boss publicly pointed it out during a team meeting. As a tech executive excelling in performance and dedicated to excellence, you’ve noticed limited recognition for hard work, which can be elusive.

While the leadership team acknowledges your ongoing efforts and contributions, it’s disheartening to note the silence from peers. Indeed, upon mentioning the mistake, you observed subtle smirks that were hard to miss, signaling a lack of support or understanding from close colleagues. Even more disconcerting was overhearing two colleagues who seemed to take delight in my error, sharing a private chuckle at your expense. This unexpected behavior prompts a deeper reflection on what drives such reactions.

Recovering from a screw up can be difficult.

But it’s important to remember that we’re all human and prone to mistakes—this is an inescapable part of our shared experience in any workplace. Unfortunately, jealousy is a common trait that often manifests in unpleasant and sometimes hurtful ways. Navigating through such situations effectively can be challenging and requires a thoughtful approach. How would you handle it in a similar scenario?

  • Remember: You are a top performer who consistently approaches work with professionalism and diligence. Don’t let one incident bring you down. Rise above it and ignore any subtle digs or snide remarks from peers; don’t let them provoke anger or self-doubt.

  • Discuss with your boss the importance of better communication when addressing issues. While informing the team about relevant issues is crucial, handling blame privately rather than publicly can create a more supportive environment.

  • Show your peers the right way to respond when a teammate faces similar challenges. Approach them privately with empathy, reminding them of their humanity, and offering your support and understanding. This act of kindness not only helps them but sets a standard of compassion.

In conclusion, by being more compassionate than those who revel in others’ missteps, you contribute to a much healthier and more collaborative workplace culture. As a rising leader, your empathy and understanding will stand out to those in leadership roles, fostering constructive interactions. Recovering from a screw up requires acknowledging it, learning, and preventing its recurrence, turning it into a growth opportunity.

Click here for a post on about how to handle a boss who hates you.

Addressing Technical Debt

In prior posts we’ve been talking about technology strategy. Tech execs must possess a robust strategic approach to steer technology direction and secure agreement on projects and budgets within their organization. Addressing technical debt is crucial in every IT strategy. As part of our strategic building process, we include the following step:

5. Analyze Current IT Environment: A large piece of the strategy build effort occurs in this step.  Here analysis of the current environment (current state, or status quo) is documented and reviewed in order to do reflections and backward looking. 

During the current state assessment, watch out for technical debt. It’s crucial for CIOs to prioritize reducing tech debt, whether staying on the current platform or migrating to a new one.

Technical debt often stems from decisions made to expedite application deployment. It can manifest as deviations from project specifications, reliance on outdated technologies, or even shortcuts in the supporting infrastructure. Let’s explore a few instances where technical debt tends to arise:

Unpredicted expense

As pressure mounts for teams to deliver quickly, especially for applications on a lengthy development roadmap, evolving business needs may necessitate accelerated release schedules. This pressure can tempt teams to resort to shortcuts, such as hardcoding IP addresses, limiting logic flexibility and hindering future application transition to the cloud.

Evolving technology

During the system’s initial release, the technology choices were appropriate. However, the aging infrastructure requires maintenance over time. As applications become older, changes become more likely. Upgrading the operating system or supporting software may be costly but necessary for effective system operation.

Misunderstandings cause tech debt

Incomplete business requirements result in rework. Improperly documented and misunderstood application support processes cause user frustration and costly errors. Effective communication with experienced professionals prevents technical debt. A resource management plan provides valuable, low-cost support for applications.

Addressing technical debt is a delicate balance between cost and quality to meet business deadlines. If left unchecked, it hampers speed and agility in addressing business needs, gradually accumulating as the application ages.

See the next post for idea on how to eliminate Technical Debt.

Click here for a post on Total Cost of Ownership (TCO).

error: Content is protected !!