lno-time-management-framework
Categorize tasks into Leverage (10x), Neutral (1x), and Overhead (
Découvrez les skills devops project management, comparez leurs dépôts et consultez leurs instructions.
Categorize tasks into Leverage (10x), Neutral (1x), and Overhead (
Shift from rigid roles (PM, Designer, Engineer) towards a model where individuals use AI to bridge skill gaps, enabling smaller and flatter teams. Use in early-stage startups or innovation units where speed is...
A hierarchical framework forcing alignment from top down—Mission, Company Strategy, Product Strategy, Roadmap, Goals. Strategy precedes goals; goals measure progress against a strategy.
Use before starting a company with co-founders, when bringing on a new co-founder, or annually as a relationship health check to prevent the 65% of startup failures caused by co-founder conflict
Use when navigating large organizations where official strategy seems doomed but leadership isn't ready to hear it, when dealing with status updates that feel disconnected from reality, or when feeling burned o...
A feedback approach where the manager acts as a curious investigator rather than an authoritarian expert, using observation and questions to help direct reports self-diagnose issues. Use during 1:1s and perform...
Stop optimizing for positive ROI and start focusing on minimizing opportunity cost—choosing the BEST possible use of time, not just a good one. Use during quarterly planning and roadmap prioritization.
Instead of waiting for a post-mortem after failure, imagine the project has already failed spectacularly and work backward to uncover hidden risks. Use before kicking off any major initiative, product launch, o...
High-growth careers are J-Curves, not stairs—you jump off a cliff (take risk), struggle for 6-9 months (bottom of J), then shoot up exponentially. Use when deciding between safe promotion vs stretch role.
Use when delivering difficult feedback (performance issues, firing, promotion denial), when managers avoid necessary conversations due to fear, or when needing structured scripts for high-stakes communication
In scaling companies, once you master a role you must hand it off and move to a bigger, messier challenge. Holding on buries you; giving away allows you to tackle bigger challenges.
Use during quarterly or annual roadmap planning, when Engineering wants tech debt work while PMs want features and Leadership wants moonshots, to force explicit resource allocation
Leadership is a dynamic range. When confidence in team direction is low, temporary tactical micromanagement is the correct move—not autonomy. Teach the framework, then pull back.
Use when designing AI agent products, defining roadmaps for agentic workflows, or evaluating how to evolve AI from passive tool to proactive partner in software development
A three-part structural framework for building a scalable company—Foundation (Founding Documents), Posts & Beams (Supporting Structures), and Mechanicals (Operating Cadence). Use when moving from PMF to scaling...
Use when running experiments on platforms where user value compounds over time, when growth teams claim credit for revenue that would have happened anyway, or when short-term wins don't translate to long-term v...
A leadership cadence where the CEO/Leader reviews actual work (designs, prototypes, copy) weekly rather than just metrics or status slides. Use when feeling product quality is slipping or team is moving too slo...
A goal-setting mental model where leaders increase the target by 10x to force teams to abandon current processes and use first-principles thinking. Use during annual planning when teams default to safe, increme...
Review your calendar, color-code activities by energy impact (Green/Red), and systematically delegate draining tasks to maximize time in your Zone of Genius.
Diagnose team problems by checking structural issues (goals/roles) at the surface before diving deep into personality conflicts. 80% of team problems are structural, not personal.
Learn how to create effective project skills following opence conventions.
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
MUST use when interacting with Shortcut's project management platform to create, update, search, or retrieve stories, epics, iterations, teams, workflows, objectives, and documents.
MUST use when interacting with Shortcut's project management platform to create, update, search, or retrieve stories, epics, iterations, teams, workflows, objectives, and documents.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.