2 comments

  • tibbar6 minutes ago
    It&#x27;s interesting to take the counterfactual, what it looks like when large projects are run poorly. The answer often looks like:<p>* Poorly defined goals &#x2F; definition of success<p>* Overly-complex plans, slowly executed against<p>* A focus on issues that aren&#x27;t the real bottleneck<p>* Large cost and time overruns<p>* Project is eventually cancelled<p>I&#x27;ve had the interesting experience of watching the same type of &quot;transformation&quot; project run twice at similar companies. In the first case, the project was bogged down to the extent that I genuinely updated to believe it wasn&#x27;t possible to achieve. In the second case, I saw incredible progress &#x2F; pace with a much smaller team, pushing on all the key points with the right planning, and learned some lessons I wish I&#x27;d known on take 1.
  • leoedin1 hour ago
    This is a good article. Not because it&#x27;s got some crazy insights or radical suggestions - but because it&#x27;s pragmatic and sensible advice for any project. It definitely resonates with my experience - the biggest risk is just losing focus or losing track of what you&#x27;re meant to do.<p>It&#x27;s refreshingly free of buzzwords and rigid &quot;process&quot; too!
    • sdf2erf1 hour ago
      Yeah the hardest thing is to focus intensely and have a strong vision for what exactly the output should be directionally. The second hardest is actually getting the project finished - that requires sustained intense focus.<p>Theres nothing more to it than that. Frameworks etc blah blah blah. Who cares. Get the work done.