ITML IT Leadership Q&A Resource Center:
IT Performance and Self-Assessment

Return to the main IT Leadership Knowledge Base page

Table of Contents

• How do I measure IT leadership success?
• How do I know if I’m a good IT manager?
• What does a 360-degree review look like for IT managers?
• How do I set goals for myself as a new IT leader?
• What are common mistakes new IT managers make?
• How do I get honest feedback from my team?

How do I measure IT leadership success?

Measuring IT leadership success requires evaluating multiple dimensions beyond purely operational or technical metrics, recognizing that effective leadership manifests through team performance, organizational impact, and personal growth in ways that require broader assessment than purely quantitative operational measurement alone.

Team performance and health metrics provide important, if indirect, evidence of leadership effectiveness, including team productivity and delivery performance relative to expectations, employee engagement and satisfaction indicators, and team retention rates, since sustained strong team performance and health typically reflects effective underlying leadership, even though these metrics are influenced by numerous factors beyond leadership alone.

Stakeholder satisfaction and relationship quality with business partners, peer leaders, and senior executives provides valuable perspective on leadership effectiveness, since strong IT leadership typically manifests through positive stakeholder relationships and perception, beyond purely internal team-focused metrics, reflecting effective external communication, relationship building, and genuine business partnership.

Individual development and growth of your team members represents an important, often underappreciated leadership success indicator, including promotion rates and career advancement of team members you’ve led, skill development and capability growth you’ve fostered within your team, and genuine testimonials or feedback from current or former team members about your impact on their professional development.

Achievement of strategic objectives and successful initiative delivery provides tangible evidence of leadership effectiveness, particularly for more senior IT leadership roles where strategic contribution becomes increasingly important relative to purely operational management, including successful major project or transformation delivery, and genuine contribution to broader organizational strategic priorities.

Self-assessment through honest personal reflection provides valuable, if inherently subjective, perspective on your own leadership growth and effectiveness over time, including reflection on specific leadership challenges you’ve navigated successfully, ongoing development in areas you’ve previously identified as growth priorities, and genuine satisfaction and fulfillment you derive from your leadership role, which, while not purely objective, provides important personal insight into your leadership journey.

External validation and feedback mechanisms, including formal performance reviews, 360-degree feedback processes if available within your organization, and informal feedback from mentors, peers, or your own manager, provide valuable outside perspective that complements your own self-assessment, helping counteract natural biases in purely self-directed evaluation.

Recognize that leadership success metrics should be evaluated over appropriate time horizons, since some leadership impact, particularly regarding team development and organizational culture, often takes considerable time to fully manifest and may not be adequately captured through short-term metrics alone, requiring patience and longer-term perspective alongside more immediate performance indicators.

Finally, avoid over-reliance on any single success metric, instead considering a balanced portfolio of indicators spanning team health, stakeholder relationships, individual development impact, strategic contribution, and honest self-reflection, since effective leadership manifests across multiple dimensions that resist reduction to any single, simple success metric, requiring thoughtful, multidimensional assessment to genuinely understand your leadership effectiveness and ongoing development.

How do I know if I’m a good IT manager?

Determining whether you’re an effective IT manager requires honest, multidimensional self-assessment combined with genuine external feedback, since purely internal self-perception, without external validation, can be significantly biased in either overly positive or overly critical directions.

Consider your team’s genuine engagement and performance as important, if imperfect, indicators, including whether your team members appear genuinely engaged and motivated in their work, whether your team consistently delivers expected results and meets performance expectations, and whether you experience reasonable team retention, recognizing that some turnover is normal and healthy, but persistent excessive turnover, particularly of your strongest performers, often indicates genuine management concerns requiring attention.

Seek genuine, honest feedback directly from your team members, ideally through both formal mechanisms like structured feedback surveys if available, and informal, ongoing conversation where you genuinely invite honest input about your management effectiveness. This requires creating genuine psychological safety for honest feedback, since team members may hesitate to provide genuinely critical feedback if they perceive risk in doing so, requiring deliberate effort to signal genuine openness to constructive criticism.

Evaluate your relationship and reputation with stakeholders beyond your immediate team, including peer managers, senior leadership, and business partners who interact with your team, since positive stakeholder perception, while not the only relevant indicator, often reflects effective leadership including strong team performance, and effective communication and relationship management on your part.

Reflect honestly on specific management challenges you’ve navigated, considering how effectively you’ve handled difficult situations like performance management conversations, team conflicts, or significant organizational changes, since your genuine effectiveness in navigating these more challenging management moments often provides more meaningful insight than how things go during easier, less demanding periods.

Consider whether you’re genuinely developing your team members, reflecting on whether team members under your leadership show meaningful skill growth and career advancement over time, and whether former team members, if any have moved on to other opportunities, generally speak positively about their experience working for you and specific value they gained from your leadership.

Seek formal feedback mechanisms if available within your organization, including structured performance reviews, 360-degree feedback processes, or employee engagement survey results specific to your team, which provide more structured, sometimes more candid feedback than purely informal conversation alone might elicit.

Engage a mentor or trusted peer for honest external perspective, since sometimes those outside your direct reporting relationship can provide valuable, more objective observation and feedback about your management approach and effectiveness than either your own self-assessment or feedback from your direct reports, who may have some hesitation providing fully candid feedback given the inherent power dynamic in your relationship with them.

Finally, recognize that genuinely effective management is an ongoing developmental journey rather than a fixed state you either have or haven’t achieved, meaning the more productive question may be less about definitively determining whether you’re currently “good” and more about genuinely committing to ongoing learning, seeking honest feedback, and continuous improvement in your management practice over time, regardless of your current level of effectiveness.

What does a 360-degree review look like for IT managers?

A 360-degree review for IT managers provides comprehensive feedback gathered from multiple perspectives, including direct reports, peers, senior leadership, and sometimes internal or external stakeholders, offering more complete insight into management effectiveness than feedback from any single source alone, such as purely top-down performance reviews from your own manager.

The process typically begins with identifying appropriate feedback providers across different relationship categories, usually including several direct reports who work most closely with you, peer managers or colleagues who interact regularly with you, your own direct manager, and sometimes key stakeholders such as business partners who regularly interact with your team, providing genuinely diverse perspective on your leadership effectiveness across different relationship contexts.

Feedback is typically gathered through structured surveys covering specific leadership competencies relevant to IT management roles, such as communication effectiveness, delegation and empowerment, technical credibility, strategic thinking, and specific behavioral indicators relevant to each competency area, often using rating scales alongside open-ended questions that allow more detailed, specific feedback beyond purely numerical ratings.

Anonymity for feedback providers, particularly direct reports, is typically emphasized to encourage more honest, candid feedback than might otherwise be provided if feedback providers feared their specific comments might be directly attributed to them, given the inherent power dynamics in providing feedback about your direct manager or other organizational relationships.

Results are typically compiled and presented in aggregate form, often organized by feedback source category, such as direct reports, peers, and manager feedback presented separately, allowing you to identify whether perception differs significantly across these different relationship categories, which can provide valuable insight into specific relationship dynamics requiring particular attention.

The review typically includes comparison against self-assessment ratings you provide for the same competency areas, highlighting any significant gaps between how you perceive your own leadership effectiveness and how others actually experience your leadership, which often provides some of the most valuable insight from the entire 360-degree process, since significant self-perception gaps often indicate blind spots particularly worth addressing.

Following receipt of 360-degree feedback results, most effective processes include structured debrief conversation, often facilitated by a coach, HR professional, or your own manager, helping you process and make sense of the feedback constructively, since raw 360-degree feedback data alone, without appropriate context and support for interpretation, can sometimes feel overwhelming or be misinterpreted without proper facilitation.

Development planning typically follows the feedback and debrief process, translating specific insights from your 360-degree results into concrete development priorities and action plans, ensuring the significant effort invested in gathering comprehensive feedback translates into genuine behavior change and improvement rather than simply providing interesting but ultimately unused information.

Finally, effective 360-degree review processes typically include some mechanism for follow-up and progress tracking over time, whether through periodic informal check-ins, subsequent 360-degree assessments after a defined period, or ongoing coaching support, ensuring the valuable insight gained through this comprehensive feedback process genuinely translates into sustained leadership development and improvement rather than being a single point-in-time assessment without meaningful follow-through and behavior change over time.

How do I set goals for myself as a new IT leader?

Setting effective goals as a new IT leader requires balancing ambition with realistic prioritization, focusing on genuine developmental priorities rather than attempting to address every possible improvement area simultaneously during your critical early period in a new leadership role.

Begin by conducting honest self-assessment of your current strengths and development areas, ideally incorporating feedback from your own manager, mentors, or trusted colleagues who can provide external perspective beyond purely self-directed assessment, ensuring your goal-setting genuinely addresses meaningful development priorities rather than being based solely on your own potentially incomplete self-perception.

Distinguish between different categories of goals relevant to new leadership roles, including team performance goals related to specific operational or project outcomes your team needs to achieve, personal leadership development goals focused on your own skill growth in areas like communication, delegation, or strategic thinking, and relationship-building goals focused on establishing effective working relationships with your team, peers, and senior stakeholders.

Prioritize a manageable number of specific goals rather than attempting to address numerous development areas simultaneously, particularly during your critical early period in a new role where attention and energy are already significantly consumed by the fundamental demands of establishing yourself in a new position. Typically, focusing on two to four genuinely priority goals tends to be more effective than a more extensive goal list that risks diluting focus across too many simultaneous priorities.

Ensure your goals are specific and measurable wherever possible, avoiding vague aspirational statements in favor of concrete, assessable objectives, such as specific team performance metrics you’re targeting, particular leadership behaviors you’re committing to develop and practice, or specific relationship-building milestones you’re pursuing with key stakeholders.

Establish realistic timelines that account for your limited tenure and understanding during early leadership periods, recognizing that some goals, particularly those involving significant team or organizational change, may require longer timeframes than goals focused on your own individual skill development or relationship building, which might show more immediate progress.

Seek input and alignment from your own manager regarding your goals, ensuring your self-identified priorities genuinely align with their expectations and broader organizational priorities, rather than pursuing goals that, however personally meaningful, might not align well with how your performance will actually be evaluated by your own leadership.

Build in regular reflection and goal reassessment, recognizing that your understanding of genuine priorities and development needs will likely evolve significantly as you gain more experience and context in your new role, meaning initial goals set during your first weeks or months may require meaningful adjustment as your understanding deepens over time.

Consider incorporating both outcome-focused goals, related to specific results you’re aiming to achieve, and process-focused goals related to specific behaviors or practices you’re committing to develop, since focusing exclusively on outcomes without attention to the specific behavioral changes required to achieve them sometimes provides insufficient guidance for your actual day-to-day leadership practice.

Finally, maintain appropriate self-compassion and realistic expectations, recognizing that meaningful leadership development, particularly for genuinely new leaders, typically requires sustained effort over an extended period rather than rapid transformation, and setting overly ambitious goals without acknowledging the genuine learning curve involved in leadership development can create unnecessary pressure and potential discouragement if progress doesn’t match unrealistic initial expectations.

What are common mistakes new IT managers make?

New IT managers commonly encounter several predictable pitfalls as they transition from individual technical contributor roles into management responsibility, and awareness of these common mistakes can help new managers proactively avoid or at least minimize their impact.

Continuing to personally handle technical work rather than genuinely delegating represents one of the most common and significant mistakes, as many new managers, particularly those promoted specifically for their strong technical skills, struggle to release direct technical involvement, continuing to personally solve problems rather than developing their team’s capability to handle these challenges independently, ultimately limiting both their own capacity for genuine management work and their team’s professional growth.

Failing to adjust communication style appropriately for a management role represents another common challenge, as new managers sometimes continue communicating as they did as individual contributors, providing insufficient context or strategic framing that their new management role and expanded stakeholder relationships actually require, rather than developing the more versatile, audience-appropriate communication style effective management demands.

Avoiding difficult conversations, whether related to performance issues, conflict resolution, or other challenging management responsibilities, represents a common pitfall, particularly for new managers uncomfortable with the interpersonal friction these conversations can create, leading to problems that persist or worsen due to avoided rather than proactively addressed management responsibilities.

Attempting to be everyone’s friend rather than establishing appropriate management authority and boundaries, particularly challenging for managers promoted from within their existing team, can undermine necessary management effectiveness, as new managers sometimes struggle to balance genuine care for their team members as people with the appropriate authority and occasionally difficult decisions effective management requires.

Making too many changes too quickly, without adequately understanding existing context and team dynamics, represents another common new manager mistake, as eager new leaders sometimes rush to implement their own ideas and preferred approaches before genuinely understanding why existing practices developed as they did, potentially disrupting effective existing practices or generating unnecessary resistance through premature change.

Neglecting to invest sufficient time in relationship-building and stakeholder management beyond their immediate team represents a common oversight, as new managers sometimes focus disproportionately on internal team management while inadequately investing in broader organizational relationships with peer managers, senior leadership, and business stakeholders that effective management ultimately requires.

Failing to seek adequate support and guidance during their leadership transition, whether through formal training, mentorship, or honest conversation with their own manager about challenges they’re encountering, represents another common mistake, as new managers sometimes attempt to navigate the significant leadership transition entirely independently, missing valuable support that could accelerate their development and help them avoid otherwise predictable mistakes.

Providing insufficient recognition and feedback to team members, particularly positive recognition for good work, represents a common gap, as new managers focused heavily on operational execution and their own performance sometimes underinvest in the ongoing feedback and recognition that significantly influences team engagement and performance.

Finally, unrealistic self-expectations regarding how quickly they should master management responsibilities represents a common internal challenge, as new managers sometimes expect themselves to immediately excel at management despite this representing a genuinely significant skill transition requiring time and experience to develop, potentially creating unnecessary self-imposed pressure and discouragement if early performance doesn’t match unrealistic expectations for immediate management mastery.

How do I get honest feedback from my team?

Getting genuinely honest feedback from your team requires deliberately creating psychological safety and demonstrating authentic openness to critical feedback, since the inherent power dynamic in manager-employee relationships naturally creates hesitancy for team members to provide fully candid feedback without deliberate effort on your part to counteract this natural reluctance.

Begin by explicitly and repeatedly inviting feedback, making clear through both direct statements and consistent behavior that you genuinely want honest input, including constructive criticism, rather than assuming team members will proactively volunteer critical feedback without explicit invitation and reassurance that such feedback is genuinely welcome.

Model receptiveness to feedback by responding constructively when team members do provide critical input, avoiding defensive reactions, dismissiveness, or any behavior that might discourage future honest feedback. How you respond to initial instances of critical feedback significantly influences whether team members feel safe providing similarly honest feedback in the future, making your response to early feedback attempts particularly important for building longer-term psychological safety.

Consider anonymous feedback mechanisms, such as anonymous surveys or suggestion systems, which can help team members feel more comfortable providing genuinely honest feedback, particularly regarding more sensitive or potentially uncomfortable topics, compared to feedback provided through direct, attributable conversation alone.

Ask specific, targeted questions rather than only general, open-ended requests for feedback, since specific questions about particular aspects of your management approach or specific decisions often elicit more useful, actionable feedback than vague requests that team members may struggle to meaningfully respond to without more specific guidance about what kind of feedback would be genuinely helpful.

Create regular, ongoing opportunities for feedback rather than only soliciting input during formal, infrequent review cycles, since regular, lower-stakes feedback opportunities, such as periodic check-ins specifically focused on your management effectiveness, tend to elicit more genuine, ongoing feedback than relying solely on formal, higher-stakes annual review processes.

Consider utilizing skip-level meetings, where your own manager or another senior leader meets directly with your team members without your presence, which can sometimes elicit more candid feedback about your management effectiveness than team members might feel comfortable sharing directly with you, given the reduced power dynamic concern in this alternative feedback channel.

Demonstrate genuine follow-through on feedback received, visibly implementing changes or improvements based on team feedback where appropriate, since team members are more likely to continue providing honest feedback if they see genuine evidence that their input leads to real changes, rather than feeling their feedback is collected without meaningful response or action.

Be patient and recognize that building genuine psychological safety for honest feedback typically takes sustained time and consistent behavior, particularly if your team has previous experience with less receptive management that created hesitancy about providing candid feedback. Consistent, patient effort over time, rather than expecting immediate, fully candid feedback from initial attempts, tends to produce better long-term results.

Finally, consider formal 360-degree feedback processes if available within your organization, which provide structured, often more clearly protected anonymous mechanisms for gathering comprehensive feedback from your team and other stakeholders, potentially complementing your ongoing informal efforts to build genuine feedback culture within your direct team relationships.

Thinking of becoming an IT Managers? Click here to take our free IT Management Assessment!