Total 52,658 skills, Project Management has 1925 skills
Showing 12 of 1925 skills
Remove a future phase from roadmap and renumber subsequent phases
Audit milestone completion against original intent before archiving
Nifty integration. Manage Organizations. Use when the user wants to interact with Nifty data.
Apply Social Identity Theory to analyze how group categorization, identification, and intergroup comparison drive behavior, bias, and conflict. Use this skill when the user needs to explain in-group favoritism or out-group hostility, diagnose organizational silo dynamics, design inclusive team structures, or when they ask 'why do groups polarize', 'how does team identity affect collaboration', or 'what drives us-vs-them thinking'.
Apply Upper Echelons Theory (Hambrick and Mason, 1984) to analyze how top management team characteristics — demographics, experiences, values — shape strategic choices and organizational outcomes. Use this skill when the user needs to evaluate TMT composition effects on strategy, predict strategic direction from leadership profiles, assess whether managerial discretion enables or constrains executive influence, or when they ask 'does leadership background matter for strategy', 'how does TMT composition affect decisions', or 'why did this management team make that choice'.
Apply the three-level framework of digital transformation — Digitization, Digitalization, and Digital Transformation — to diagnose and plan organizational change enabled by digital technologies. Use this skill when the user needs to assess an organization's digital maturity, distinguish between automating processes versus transforming business models, plan a DX roadmap, or when they ask 'where are we on digital transformation', 'is this digitization or real transformation', or 'how do we build a DX strategy'.
Apply the DeLone and McLean Information Systems Success Model to evaluate IS effectiveness through six interdependent dimensions. Use this skill when the user needs to assess system quality, information quality, or service quality of an IS, diagnose why users are dissatisfied, measure net benefits of a system investment, or when they ask 'how do we measure IS success', 'why are users unhappy with this system', or 'is our system delivering value'.
Apply Sociotechnical Systems Theory to analyze and design work systems through joint optimization of social and technical subsystems. Use this skill when the user needs to diagnose why a technology implementation disrupted work practices, design IT-enabled work systems that balance human and technical needs, or when they ask 'why did this system hurt productivity despite being technically sound', 'how do we design work around new technology', or 'why are people resisting this technically superior system'.
Avaza integration. Manage Organizations. Use when the user wants to interact with Avaza data.
Generates customized client onboarding checklists with phased tasks, ownership assignments, dependencies, acceptance criteria, and email templates. Adapts to consulting, SaaS, or agency engagement models.
When the user wants to plan production or distribution capacity, analyze capacity requirements, optimize resource utilization, or balance capacity with demand. Also use when the user mentions "capacity analysis," "resource planning," "bottleneck analysis," "capacity expansion," "load balancing," "throughput planning," "utilization optimization," or "capacity modeling." For production scheduling, see master-production-scheduling. For long-term network capacity, see network-design.
Generate the competitive analysis section with competitor profiles, SWOT analysis, competitive matrix, differentiation strategy, market share positioning, and sustainable competitive advantage (moat). Proves the business can win against alternatives. Use when building or reviewing competitive analysis sections, benchmarking against competitors, or defining market positioning. Incorporates Farris's competitive metrics, guerrilla positioning strategy, value-based differentiation frameworks, Teece's business model vs strategy distinction (business model = architecture of value creation and capture; strategy = how the model is made difficult to imitate), Kaza's four differentiation types (aesthetic experience, social experience, boundary interactions, purposeful experiences), Ohmae's 3C Strategic Triangle and Key Factors for Success, and the Portable MBA onstage/backstage model with Value Net complementors framework.