How to Run Large-Scale Internet Projects Efficiently in a Remote (SOHO) Era

Background

During the pandemic, many internet companies switched to a SOHO (work‑from‑home) model while keeping operations running. Large‑scale campaigns such as Alibaba's Double 11, Alibaba Pictures' Spring Festival releases, and Youku's World Cup events test both technical skills and team collaboration.

Five Key Elements for Large Projects

Define the result → project goals.

Identify teammates → project members.

Set the timeline → project plan.

Establish collaboration → project mechanisms.

Post‑mortem and knowledge capture → retrospection.

The process is iterative: clarify objectives, find the right people, schedule, set mechanisms, and capture outcomes.

Problem Clarification by Project Phase

Initiation: define direction, confirm personnel, clarify goals, set mechanisms, create milestone plan.

Planning: confirm objectives, finalize方案, create execution plan.

Execution: monitor goals, control schedule, ensure delivery.

Monitoring: verify goals, apply mechanisms, check plans, identify risks, create contingency plans, manage changes.

Closure: orderly wrap‑up, deep retrospection, effective knowledge沉淀.

Three Management Focuses

Drive Management Nodes – keep information aligned, surface risks, and respond quickly. Effective meetings are crucial; preparation, agenda control, and post‑meeting conclusions are essential.

Ensure Communication Channels – maintain clear upstream/downstream information flow, synchronize teams, and use reliable IM, audio‑video, and screen‑sharing tools.

Apply Management Mechanisms – adopt goal‑ownership, communication, requirement‑management, and risk‑mitigation mechanisms.

Operational Process

1. Drive Management Nodes

Before meetings: gather agenda items and key inputs. During meetings: focus on agenda, control time, ensure effectiveness. After meetings: output conclusions and share with participants.

Direction‑Focus Meeting – confirm project value, core owner, and key teammates; output direction, preliminary strategy, milestones, and operating mechanisms.

Solution Review Meeting – based on direction‑focus output, present core solution draft and coordinate cross‑team business方案.

Requirement Review Meeting – clarify business需求, assign owners, and plan implementation.

Retrospective Meeting – review goals vs. outcomes, capture reusable capabilities, and follow up on issues.

Communication Channels

Daily Meeting – focus on core information, sync progress, accept deliverables, and make quick decisions.

Daily Report – record and sync goals, strategies, progress, and risks; confirm critical information with stakeholders.

Document Library – improve information management, reduce communication bottlenecks, enable autonomous team collaboration, and preserve knowledge for future retrospectives.

Establish and Use Mechanisms

Continuously focus on goals, strategies, and schedules to drive efficient execution; identify and mitigate risks with pre‑planned contingencies.

Key Points

Kick‑off Meeting (K.O.) – clarify project overview, goals, strategy, and implementation plan; ensure all departments understand their roles and cooperate efficiently.

Preparation: confirm participants, choose suitable collaboration tools (video conference, live streaming), and test equipment.

Agenda: project background, scope, product方案, management mechanisms (security, rewards, communication, change management), and formal delegation.

Principles: involve senior leaders, start and end on time, maintain a formal yet concise format, and emphasize the meeting’s importance.

Summary: document key points, share leadership remarks, team photos, and K.O. documents to drive project progress.

Risk Management

Continuously identify, report, and handle risks; foster a culture where all team members are aware of and promptly report risks.

Stakeholder Management

Identify stakeholders, analyze their requirements, and manage expectations; include both supportive and opposing parties.

Retrospective

Purpose: review goals and solutions against actual outcomes, capture reusable capabilities, and address system flaws.

Timing: after project deadline, upon achieving target, or when serious issues arise.

Principles: multi‑goal review, sub‑project retrospectives within teams, encourage open discussion while avoiding self‑praise or attacks.

Preparation: define participants, time, venue; allocate speaking slots; gather relevant data and materials.

Conclusion

By applying these practices, projects achieve predictable goals, schedulable resources, controlled changes, and traceable issues, ensuring large‑scale campaigns launch smoothly and meet expectations.