Appendix - Frameworks and models
Engineering Managers rely on structured frameworks to navigate career development, deliver effective feedback, and set clear goals. Below are three of the most powerful and widely used models in the tech industry.
SFIA Framework
The SFIA (Skills Framework for the Information Age) is a globally recognized model that defines the skills and competencies required by professionals working in IT and software engineering. It provides a common language for describing skill levels across an organization.
For an Engineering Manager, SFIA is a powerful tool for career mapping, performance reviews, and hiring. Instead of using vague expectations like "we need you to be more senior," you can map an engineer's progress against objective levels. SFIA structures skills across several core attributes:
- Autonomy: How much direction an individual needs.
- Influence: How their work impacts the team and the broader organization.
- Complexity: The technical or structural difficulty of the problems they solve.
- Business Skills: Communication, leadership, and domain knowledge.
SBI Feedback Model
The SBI (Situation-Behavior-Impact) model is a structured way to deliver clear, objective, and effective feedback. It prevents feedback from sounding like a personal attack or a subjective opinion by separating facts from feelings.
- Situation: Describe the specific time and place. This grounds the feedback in reality.
- Example: "During yesterday's architecture review meeting..."
- Behavior: Describe the observable action without interpretation or judgment.
- Example: "...you interrupted the junior engineer three times while they were presenting..."
- Impact: Describe the result or consequence of that behavior.
- Example: "...which caused them to shut down, and as a result, we missed hearing their proposed solution."
By using SBI, you give the engineer exactly what they need to understand the issue, lowering their defensive barriers and opening the door for constructive dialogue.
S.M.A.R.T. Goals
S.M.A.R.T. is an acronym used to guide goal setting, ensuring that objectives are clear, reachable, and trackable. This is essential for guiding Individual Contributors (ICs) during performance cycles and keeping the team focused.
- Specific: The goal should be well-defined and unambiguous.
- Instead of: "Improve authentication."
- Use: "Refactor the authentication module to use OAuth2."
- Measurable: You must be able to track progress and know exactly when the goal is achieved.
- Example: "Reduce average login latency by 200ms."
- Achievable: The goal must be realistic and attainable given the engineer's current skill level and available resources. Setting impossible goals destroys morale.
- Relevant: The goal should align with broader team goals, company objectives, or the individual's career growth path.
- Time-bound: There must be a clear, committed deadline.
- Example: "By the end of Q3."
🎯 Self-Reflection for You
- Have you established a clear framework like SFIA for your team so they understand exactly what is required for their next promotion?
- Think about the last piece of critical feedback you gave. Did it follow the objective SBI structure, or was it vague and interpretive?
- Review your team's current goals. Are they truly S.M.A.R.T., or are they impossible to objectively measure?
Mastering these frameworks can transform your management style from reactive to strategic. If you want to discuss how to apply them practically to your team, let's map out a plan in a virtual coffee chat.