Hasty Briefsbeta

All tags

#leadership

109 stories total

Bilingual

Tesla loses another top talent: its long-time head of software
a year ago
- Tesla's long-time head of software, David Lau, is reportedly leaving the company.
- Lau played a key role in transforming Tesla's software, making it a leader in the auto industry.
- He joined Tesla in 2012 and rose to Vice President of software by 2017.
- His team was responsible for vehicle software, distributed systems, manufacturing automation, and product security.
- Lau's departure follows a trend of top talent leaving Tesla, including after last year's layoffs.
- Potential successors include Michael Rizkalla, a senior director of software engineering at Tesla.
- Elon Musk may also integrate Lau's responsibilities under senior AI executives.
Gravity Maps: An Alternative to Org Charts
a year ago
- Org charts show formal roles but miss hidden power structures.
- A 'gravity map of influence' identifies real influencers, not just job titles.
- Influencers sway opinions and decisions regardless of their position.
- Organizational gravity isn't documented; build your own map by observing and asking colleagues.
- Update the gravity map regularly to adapt to organizational changes.
- Best articles list includes topics like research interview questions, leadership foundations, and analytics tools.
AI coding mandates are driving developers to the brink
a year ago
- Almost half of C-suite executives report AI adoption is causing internal rifts, with 75% of leaders believing their AI rollout is successful compared to only 45% of employees.
- Developers express concerns about AI coding tools introducing errors, increasing technical debt, and being hindered by misguided mandates.
- FOMO drives AI adoption, with leaders attracted to automation benefits, potential cost savings, and competitive pressure.
- Developer faith in AI coding tools is declining, with reports of incorrect code suggestions, deployment issues, and increased debugging time.
- Executives often mismanage AI expectations, imposing metrics like code acceptance rates without understanding engineering workflows.
- Empowering developers with flexibility and trust leads to better AI tool adoption, as seen in ChargeLab's 40% productivity increase.
- Effective AI adoption requires collaboration, empowerment, and fostering a culture of innovation rather than top-down mandates.
Engineers Who Won't Commit
a year ago
- Engineers should commit to decisions when they have the most context or technical skill to prevent poor choices by less informed team members.
- Non-committal behavior in technical discussions is often driven by a fear of being wrong, which can be seen as cowardice when decisions are needed.
- Managers are generally forgiving of incorrect technical calls if they are educated guesses, especially in difficult situations.
- Avoiding commitment can be smart in toxic work environments where missed estimates lead to unfair consequences.
- The article emphasizes the importance of making commitments in functional work environments, even when uncertain, to drive progress and avoid passing responsibility to others.
The thing about the Kobayashi Maru
a year ago
- The Kobayashi Maru is a simulation designed by Starfleet to teach cadets about no-win scenarios.
- The scenario punishes cadets for attempting to rescue the Kobayashi Maru, reinforcing the idea that saving civilians is not worth risking a Starfleet vessel.
- Captain Kirk argues that the Kobayashi Maru is not about accepting fate but conditioning officers to prioritize Starfleet over civilians.
- Kirk compares the Kobayashi Maru to the actions of Kodos during the Tarsus IV famine, where quick, brutal decisions were made at the expense of others.
- Kirk cheated on the Kobayashi Maru test to make a statement against its underlying message, but Starfleet never changed the simulation.
- The conversation highlights a philosophical divide between accepting hard choices and striving to find better solutions.
Dear Lewis, my CEO wants AI to do it all. How do I argue for humans?
a year ago
- A VP of Sales, Aiden, is given 48 hours to justify why AI can't replace human sales talent by his CEO, Lydia.
- The HUMAN framework is introduced to highlight irreplaceable human capabilities in sales: Hidden Context Recognition, Unified Accountability System, Motivated by Skin in the Game, Adaptive Initiative Taking, and Navigating Relationship Networks.
- Examples include detecting unspoken objections, embodying accountability, personal stakes in deals, swift adaptive actions, and navigating complex client relationships.
- AI's strengths in sales are acknowledged, such as analyzing call patterns, automating outreach, and optimizing assignments, but human elements are crucial for high-stakes deals.
- Aiden successfully convinces Lydia by demonstrating where humans outperform AI, leading to approval for additional sales managers and a budget increase for incentives.
- The key takeaway: AI excels in the science of sales, but the art—human intuition, accountability, and relationship-building—remains irreplaceable.
The Simplicity Fetish
a year ago
- Corporate simplicity fetishism is damaging and only benefits those in power.
- Complex problems require nuanced communication, not oversimplification, to avoid impedance mismatches.
- Information overload and cognitive overload create their own forms of impedance mismatch in organizations.
- Leaders often demand oversimplified summaries due to time constraints, leading to miscommunication and inefficiency.
- Instead of simplifying complex problems, focus on creating environments that support complex problem-solving.
- Effective interfaces and localized complexity can foster better collaboration and communication.
- Push decision-making closer to those doing the work to manage cognitive load.
- Resist the urge to oversimplify; first focus on the problem's core, then simplify strategically.
How to Tell Your Boss They're Wrong–Tactfully
a year ago
- Challenges in disagreeing with a boss's strategy that seems impractical.
- Importance of voicing concerns tactfully to avoid confrontation.
- Strategies for framing concerns effectively without damaging the relationship.
- Debate between asking questions versus making a direct case.
Why Narcissists Emerge as Leaders Even in Childhood
a year ago
- Narcissistic leaders are charming and assertive, inspiring confidence in uncertain times.
- They have a dark side, including unethical and aggressive behavior, stifling collaboration.
- Narcissism is characterized by grandiosity, entitlement, and a craving for admiration.
- Narcissistic children often emerge as leaders in classrooms, embodying qualities peers associate with leadership.
- Narcissistic leaders are not necessarily better leaders; they don't improve group performance.
- Children with low self-esteem are more drawn to narcissistic leaders, feeling more included and valued.
- Narcissistic leaders and followers with low self-esteem may form a symbiotic but potentially toxic relationship.
- Over time, this dynamic can lead to dependency, underperformance, and burnout in followers.
- Society values individualism, allowing narcissistic leaders to rise quickly, often mistaken for having healthy self-esteem.
- Cultivating democratic leadership skills in children can help create a new generation of effective leaders.
Lip-Bu Tan: Our Path Forward
a year ago
- Intel reported better-than-expected Q1 2025 results, exceeding revenue, gross margin, and EPS guidance.
- The company faces a volatile macroeconomic environment and must improve in several areas to stay competitive.
- Intel plans to revamp its culture to address being perceived as slow, complex, and resistant to change.
- A flatter Executive Team structure has been introduced to enhance simplicity, speed, and collaboration.
- Intel will refocus on engineering, empowering engineers by removing burdensome workflows and processes.
- Cost reductions are planned to invest in engineering talent and technology roadmaps, including operating expense and capital spending cuts.
- Organizational complexity will be reduced by removing unnecessary layers and increasing spans of control.
- Workforce reductions are expected in Q2 to streamline operations and improve efficiency.
- Processes will be streamlined to reduce time spent on internal administrative work and unnecessary meetings.
- Intel will update its hybrid work policy to require four days per week on-site by September 1, 2025.
- The company aims to build a new Intel by focusing on product development, customer satisfaction, and predictable execution.
- Lip-Bu Tan expresses confidence in Intel's ability to reinvent itself and return to being a leader in innovation.
Microsoft's Big AI Hire Can't Match OpenAI
a year ago
- Microsoft's consumer AI tool, Copilot, has stagnated at around 20 million weekly users, while ChatGPT has grown to 400 million.
- Mustafa Suleyman, hired to lead Microsoft's AI efforts, has faced skepticism and internal challenges, including underwhelming results from the MAI-1 model.
- Microsoft's $650 million deal to bring Suleyman and Inflection's talent onboard was seen as a strategic move to reduce reliance on OpenAI.
- Internal conflicts arose over the use of synthetic data in AI model training, leading to team reorganizations and departures.
- Suleyman's revamped Copilot launch was overshadowed by external events and did not significantly alter Microsoft's position in the AI race.
- Microsoft's leadership, including CEO Satya Nadella, remains supportive of Suleyman, but pressure is mounting for a successful consumer AI product.
Experts and Elites Play Fundamentally Different Games
a year ago
- Experts are judged by their technical knowledge and precision, focusing on being right within their field.
- Elites are evaluated on broader qualities like charisma, social connections, and cultural fluency, often without deep technical expertise.
- Elite institutions screen for roundedness and social impressiveness rather than narrow expertise.
- Elites often override expert opinions, especially on morally or emotionally charged issues, shaping narratives to fit their consensus.
- Promotions in organizations often reward eliteness—social fluency and political instincts—over pure technical expertise.
- During the Covid pandemic, elite consensus quickly overruled initial expert skepticism on measures like lockdowns and masks.
- Attractiveness influences career prospects differently for experts vs. elites; e.g., attractive social scientists earn more, while unattractive natural scientists do.
- Elites hide their ambition behind a facade of selflessness, while experts can be openly ambitious.
- Populist movements often reflect elite factional battles rather than genuine grassroots revolts.
- Nobel Prize winners often struggle to transition from expert to elite roles despite their credentials.
Apple Turnover
a year ago
- Ambrosia Software's philosophy: Virtue leads to money and good things, not the other way around.
- Apple's success was built on prioritizing great products over profits, but recent decisions suggest a shift in focus.
- Apple's leadership has increasingly prioritized control, leverage, and profits over product quality and customer experience.
- Examples include restrictive App Store policies, high upgrade costs, and resistance to competitive features like in-app Kindle purchases.
- Apple's internal culture appears resistant to change, with leadership doubling down on controversial decisions despite legal and public backlash.
- The author argues that Apple needs new leadership to realign with its original virtuous cycle of product excellence driving success.
Google Doc Templates for Startups
a year ago
- Decision doc - for group alignment on type 2 decisions.
- Retro doc - for improving team cohesion and processes periodically or after incidents.
- Strategy doc - for setting, communicating, and aligning on strategy.
- Project tracker - for tracking tasks and communicating project status.
- Investigation doc - for exploring unclear problems.
- Direct report 1:1 - template for effective manager one-on-ones.
- All-hands slides - basic slides for regular large group meetings.
- Roles & Responsibilities clarifier - resolves ambiguity over responsibilities.
- PRD - source-of-truth for product improvement proposals.
- Readout - analysis of product change performance in the market.
- Product vision doc - outline for a compelling vision statement.
- Leveling guide - generic product management leveling guide.
- Interview exercise - sample PM interview exercise (consumer + design-oriented).
- Author is a product leader and ex-CEO/founder at Keeper (~8 digit ARR, $15M raised, profitable).
- Author prefers documenting repetitive information.
Introducing Myself
a year ago
- New Executive Director expresses excitement and gratitude for joining the GNOME Foundation.
- Background includes extensive experience in software development, open source, and startups, with a personal story of overcoming partial blindness.
- GNOME's mission as a universal computing environment is highlighted as a key inspiration.
- Emphasis on the importance of community, transparency, and celebrating contributors.
- Goals include enhancing financial stability, resilience, and supporting GNOME's growth for the future.
I Infiltrated the Corporate Caste System (and You Can Too, but You'll Hate It)
a year ago
- The author recounts an experience in Europe where they were judged based on being from Mississippi, highlighting how labels can lead to quick judgments.
- Corporate life, especially in tech, is critiqued for its superficiality, with leadership often being about appearances rather than substance.
- The author describes a tech company where leadership was recycled from old jobs, creating a clique-like environment filled with corporate jargon.
- Middle management is criticized for creating unnecessary work to justify their roles, rather than contributing meaningfully.
- The author contrasts their fiancée's tangible, hard work as a house cleaner with the often intangible and overvalued work in corporate settings.
- Success in corporate environments is portrayed as dependent on optics, connections, and playing the game rather than skill or results.
- The author concludes by sarcastically suggesting to adopt corporate lingo and personas to succeed, despite the system's flaws.
What do executives do, anyway? (2019)
a year ago
- Executives define and enforce company culture and values, and ratify good decisions rather than making them.
- The decision-making algorithm involves leads presenting a unified decision to the lowest common executive for ratification.
- Executives must enforce company values strictly, correcting or removing those who don't align, to prevent cultural decay.
- Strategy in large organizations is not set by executives but emerges from enforced values that guide employee decisions.
- Small companies operate differently, with founders often deeply involved in decisions and strategy still being formed.
- Major strategic changes require new values, often leading to executive turnover and significant organizational disruption.
- Effective organizational values involve clear tradeoffs, not generic statements, to guide decision-making under pressure.
- Government inefficiencies mirror corporate issues when values aren't enforced, highlighting the role of propaganda in shaping public values.
Apple Turnaround
a year ago
- Apple needs significant changes but lacks the crisis to motivate current leadership.
- Developers are dissatisfied with Apple due to lack of respect and trust, not just financial issues.
- Apple should improve App Review, create a public bug tracker, and allow third-party payment methods.
- Apple's software reliability has declined, with leadership prioritizing new features over bug fixes.
- Apple's focus on services revenue growth is eroding its core product-focused philosophy.
- Apple could grow by attracting Android users with better, more affordable iPhones.
- New leadership is needed to address these issues, as current leaders seem unwilling to change.
Stuff I Learned at Carta
a year ago
- Working in the details: Transitioning from high-level abstraction to deep involvement in details was a key learning.
- Refining engineering strategy: Authored a book on engineering strategy, with practical experience gained at Carta.
- Extracting the kernel: Emphasized the importance of understanding executive communication from the receiver's perspective.
- Adopting LLMs: Led the adoption of LLMs in business-impacting workflows and explored new product capabilities.
- Multi-dimensional tradeoffs: Learned to navigate complex decisions by considering multiple layers of context.
- Navigators program: Successfully implemented a program to ensure senior engineers had direct representation.
- Software quality: Developed insights into building high essential complexity systems.
- Engineering costs: Refined strategies for managing engineering salary costs and explaining R&D investments to boards.
- Smaller learnings: Included policies like 'no wrong doors' and understanding career motivations ('Act Two').
Five opinions I've kept, let go, and picked up as a software builder and leader
a year ago
- Typed languages are better for refactoring and maintaining large codebases.
- Engineering managers must be technical to effectively lead and understand their teams.
- Continuous Deployment is essential for high-performing teams to deliver quickly and efficiently.
- Writing is a superpower for clarity, iteration, and documentation.
- Hiring QAs is dysfunctional; instead, invest in automation and observability.
- Scala is no longer the best JVM language due to its complexity and community direction.
- Deadlines are beneficial as they encourage creativity and prevent overengineering.
- Fine-graining tasks too early can be counterproductive; autonomy and understanding scope are better.
- Test coverage and unit tests are not always necessary; integration tests and observability are more valuable.
- Preproduction environments identical to production are often impractical and costly.
- Support is critical for internal Platform teams to build trust and influence.
- Providing support where people are (e.g., Slack) shows user centrism and improves satisfaction.
- Shipping builds momentum and trust, while complaining creates distrust.
- Infrastructure teams should focus on easing migrations with automation and seamless transitions.
- Brag documents are more effective than traditional performance reviews for highlighting impact and receiving feedback.

firstprev0next

About|Login

#leadership

Tesla loses another top talent: its long-time head of software

Gravity Maps: An Alternative to Org Charts

AI coding mandates are driving developers to the brink

Engineers Who Won't Commit

The thing about the Kobayashi Maru

Dear Lewis, my CEO wants AI to do it all. How do I argue for humans?

The Simplicity Fetish

How to Tell Your Boss They're Wrong–Tactfully

Why Narcissists Emerge as Leaders Even in Childhood

Lip-Bu Tan: Our Path Forward

Microsoft's Big AI Hire Can't Match OpenAI

Experts and Elites Play Fundamentally Different Games

Apple Turnover

Google Doc Templates for Startups

Introducing Myself

I Infiltrated the Corporate Caste System (and You Can Too, but You'll Hate It)

What do executives do, anyway? (2019)

Apple Turnaround

Stuff I Learned at Carta

Five opinions I've kept, let go, and picked up as a software builder and leader