¿Qué es SMART en gestión de proyectos?
- 1. Fundamentos de la gestión de proyectos
- 2. Metodologías de gestión de proyectos
- 3. Ciclo de vida de un proyecto
- 4. Software de gestión de proyectos
- 5. Consejos para el trabajo en equipo
- 6. Fundamentos de la metodología Agile
- 7. Herramientas y técnicas de gestión de proyectos Agile
- 8. Marcos de gestión de proyectos
- 9. Recursos
- 10. Glosario
- 11. Preguntas frecuentes
- 1. Fundamentos de la gestión de proyectos
- 2. Metodologías de gestión de proyectos
- 3. Ciclo de vida de un proyecto
- 4. Software de gestión de proyectos
- 5. Consejos para el trabajo en equipo
- 6. Fundamentos de la metodología Agile
- 7. Herramientas y técnicas de gestión de proyectos Agile
- 8. Marcos de gestión de proyectos
- 9. Recursos
- 10. Glosario
- 11. Preguntas frecuentes
¿Qué es SMART en gestión de proyectos?
SMART se refiere a los criterios para establecer metas y objetivos, es decir, que estos objetivos son: Specific (específicos), Measurable (cuantificables), Attainable (alcanzables), Relevant (pertinentes) y Time-bound (de duración determinada). La idea es que cada objetivo del proyecto debe cumplir con los criterios SMART para ser efectivo. Por lo tanto, al planificar los objetivos de un proyecto, cada uno de ellos debe ser:
- Specific (específico): el objetivo debe abordar un área específica de mejora o responder a una necesidad concreta.
- Measurable (cuantificable): el objetivo debe ser cuantificable o al menos permitir un progreso que se pueda medir.
- Attainable (alcanzable): el objetivo debe ser realista y basarse en los recursos disponibles y las limitaciones existentes.
- Relevant (pertinente): el objetivo debe alinearse con otros objetivos empresariales para que se considere conveniente.
- Time-bound (de duración determinada): el objetivo debe tener una fecha límite o un final definido.
Lectura adicional:

What are SMART goals?
Specific
The goal should target a specific area of improvement or answer a specific need. Because it’s the first step in the SMART goal process, it’s important to be as clear as possible. For example, note the difference between “I will make lunch” and “I will use wheat toast, peanut butter, and strawberry jam to create a tasty sandwich for myself to eat”. See how specific it is? This example also illustrates the importance of word choice. Not only are you noting which ingredients or tools will be used to achieve the final goal, but you’re also articulating who benefits. Details like these color your goal description, making it easier for collaborators to visualize and align intentions with your project.
Measurable
The goal must be quantifiable, or at least allow for measurable progress. In this step, you’ll choose what your progress markers or project KPIs are and how you’ll measure them. This might mean adopting the right tools or restructuring your KPI’s to something that you can easily monitor. You’ll also need to define who is in charge of measuring your progress, when these measurements will take place, and where the information will be shared.
Attainable
The goal should be realistic and based on available resources and existing constraints. Typical project constraints include team bandwidth, budgets, and timelines. Project managers should look to data from similar past projects for insight into what’s achievable this time around.
Relevant
The goal should align with other business objectives to be considered worthwhile. You can also break your project goal down into smaller, equally relevant goals that will keep the whole team focused. Be diligent about eliminating irrelevant goals and subgoals to save significant time.
Time-bound
The goal must have a deadline or a defined end. This can be measured in hours and minutes, business days, or years depending on the project scope. To set your project timelines, get feedback from major stakeholders about their deadline expectations, and compare it to team members' inputs.
You can write down your SMART goals and share them with your team using a shared document or an OKR template. An OKR template allows you to identify, build, discuss, track, and rate goals for both teams and individuals on any given project.

Acaba con los obstáculos, consigue claridad y supera los objetivos
Todo es posible con el software de gestión del trabajo más eficaz a tu alcance.

Where did the idea of SMART goals come from?
Although the term SMART first appeared in a 1981 issue of a business management magazine, SMART goals were born from a 1960s psychological theory where researchers began testing the relationship between conscious decision-making and output. In Dr. Edwin Locke’s often-quoted paper on the subject, he notes that “an individual's conscious ideas regulate his actions” and have a direct relationship to goal execution.
His study also finds that it isn’t money, results, or external pressures that motivate high performance. It’s simply the act of breaking down a hard goal into a conscious purpose that others willingly share. Although you can’t force someone to be excited about a project, you can set them up for success with highly structured objectives using the SMART goal method.
Examples of SMART goals for project managers
As you’ll see from the below examples, SMART goals can be applied to all aspects of project management. Simplifying your SMART goal into one simple sentence is a powerful tool for aligning your whole team around a shared intention.
- Adopt a work management tool (specific) that organizes at least 50 (measurable) incoming work requests per week (attainable) so that our team can streamline task assignment (relevant) within 30 days of receipt (time-bound).
- Create a social media marketing campaign template (specific) that plans out one daily Tweet for the next 30 days (measurable and attainable) to increase existing audience engagement (relevant) before our launch on the first of the upcoming month (time-bound).
- Realign the current project deliverables schedule (specific) by assigning new due dates to all three small tasks (measurable) over the next seven days (attainable) so that the original deadline remains the same (relevant) and clients can review the tasks by Friday (time-bound).