Efficert Academy

Day: 13 August 2024

  • “Would You Write Me a LinkedIn Recommendation Please?”

    “Would You Write Me a LinkedIn Recommendation Please?”

    The Relevance of LinkedIn Recommendations in Today’s Job Market

    In the professional landscape, the practice of requesting LinkedIn recommendations has become commonplace. Many individuals, including former students of mine, frequently ask, “Would you write me a recommendation, please?” This trend stems from the belief that such endorsements can significantly enhance one’s professional profile. This perception, however, warrants a critical examination.

    Having been a hiring manager for several years, and having engaged in numerous discussions with other hiring and HR professionals, I can affirmatively state that LinkedIn recommendations are not as influential as many believe. Here are some reasons why:

    1. Selective Endorsements: Individuals typically request recommendations from those who they believe will provide positive feedback. Consequently, these endorsements often lack critical insights and may not present an accurate reflection of a candidate’s capabilities and performance.
    2. Organizational Reference Checks: Companies have their own reference-checking protocols. These processes, whether they are effective or not, are designed to verify a candidate’s qualifications and suitability for a role. Organizations prefer to contact references directly, ensuring they receive candid and relevant information, rather than relying on a LinkedIn recommendation written by someone they do not know.
    3. Misalignment with Job Requirements: LinkedIn recommendations may not always address the specific skills and attributes that hiring managers are looking for. These endorsements often focus on general praise, which may not align with the qualifications and competencies required for a particular position.

    Given these considerations, placing undue pressure on your contacts to write a recommendation may not be the best strategy. Instead, I advise maintaining strong, genuine connections within your network. When the time comes, ask your contacts if they would feel comfortable being a reference for you when approached by potential employers. This approach is more respectful of their time and positions you in a more professional and credible light.

    By fostering authentic relationships and ensuring your references are willing and prepared to speak on your behalf, you demonstrate a higher level of professionalism and integrity. Your network will also appreciate being asked to provide support in a comfortable and authentic way.

    In conclusion, while LinkedIn recommendations may appear to enhance your profile, their actual impact on hiring decisions is limited. Focusing on building meaningful professional relationships and securing genuine references is a more effective and professional strategy.

  • The Hammer and Nail of Project Management: Agile vs. Predictive.

    The Hammer and Nail of Project Management: Agile vs. Predictive.

    Common Misconceptions and Myths Surrounding the Selection of Project Management Development Approaches and Their Impact on Project Success

    In the world of project management, there’s a debate that often feels like choosing between a fork and a spoon, or perhaps even a knife and chopsticks. It’s the debate between Agile and Predictive (or Waterfall) project management development approaches. Borrowing from the wisdom of Abraham Maslow, who said, “If the only tool you have is a hammer, you tend to see every problem as a nail,” it becomes clear that having a diverse toolkit is crucial for addressing the varied challenges of project management.

    Understanding Agile and Predictive Project Management

    Agile Project Management is often hailed as the modern, flexible approach to handling projects. Agile focuses on iterative progress, collaboration, and adapting to change. It’s like using a Swiss Army knife – versatile, adaptable, and suitable for a range of tasks. Agile methodologies, such as Scrum and Kanban, emphasize delivering small, functional pieces of a project in frequent increments, allowing teams to adapt to feedback and changes quickly.

    On the other hand, Predictive Project Management (often referred to as Waterfall) is the tried-and-true approach that emphasizes structure and predictability. It’s like using a well-honed chef’s knife – precise, reliable, and effective for tasks that require a clear, step-by-step process. Predictive methodologies involve detailed upfront planning and sequential execution of project phases, ensuring each stage is completed before moving on to the next.

    The Myth of Superiority

    There’s a common misconception that one methodology is inherently better than the other. Some view Agile as superior because it’s newer and more adaptable, while others champion Predictive for its structured, disciplined approach. However, this is a false dichotomy. The truth is, that the best approach depends on the specific needs and complexities of the project, the stakeholders’ requirements, the amount of upfront information available, and the level of changes we expect down the road!

    Choosing the Right Tool for the Job

    Imagine trying to eat soup with a fork – you might get a few pieces of solid food, but you’ll miss out on most of the meal. Similarly, trying to eat a steak with a spoon would be equally frustrating. Each tool has its place, and so do Agile and Predictive development approaches..

    When to Use Agile:

    • Dynamic Requirements: Agile is ideal for projects with evolving requirements. If stakeholders are likely to change their minds or the market is rapidly shifting, Agile allows for adjustments without derailing the entire project.
    • Incremental Delivery: When early and continuous delivery of valuable increments is crucial, Agile shines. It keeps stakeholders engaged and ensures the project is always moving forward.
    • High Collaboration: Agile thrives in environments where close collaboration between cross-functional teams and stakeholders is possible and encouraged.

    When to Use Predictive:

    • Clear Objectives: Predictive is best when the project’s goals and requirements are well-understood from the start. If you have a clear vision and little likelihood of change, this method provides a structured path to success.
    • Complex Dependencies: For projects with complex interdependencies where each phase relies heavily on the completion of the previous one, Predictive ensures a logical and orderly progression.
    • Risk Management: In situations where risk management through thorough upfront planning is paramount, Predictive methodologies offer the control and foresight needed to mitigate potential issues.

    The Hybrid Approach

    In reality, many projects benefit from a hybrid approach, blending elements of both Agile and Predictive methodologies. This hybrid model allows project managers to tailor their approach to the unique demands of each project, ensuring the right balance of flexibility and structure.

    Conclusion

    Just as a skilled chef knows when to use a knife, a fork, or a spoon, a savvy project manager understands that both Agile and Predictive approaches have their place. The key is not to view one as superior to the other but to recognize the strengths and applications of each. By having a diverse toolkit and knowing how to use each tool effectively, project managers can ensure the success of their projects, regardless of the methodology.

    So, the next time you find yourself amid the Agile vs. Predictive debate, remember: it’s not about the tool itself, but how and when you use it. After all, in the words of Maslow, if the only tool you have is a hammer, you tend to see every problem as a nail – and no project should be treated so one-dimensionally.

    If you want to learn more about this debate, you can watch a session I presented at a PMI conference on the same topic here.