{ "schemaVersion": "aaawteam-public-v2", "generatedFrom": "去敏白名单、代表性原文复核与《穷学生宝典（第一版）》去敏拆卡", "records": [ { "id": "aaaw-book-recruit-four-rounds", "title": "招新四轮考核流程", "domain": "新生必修", "summary": "用演讲、个人技术、组队技术与终面四轮考核，把招新、技术入门和意志筛选合并成一套可持续流程。", "plainLanguage": "招新不是收简历。候选人边学边考，考核本身就是第一课；能走完四轮的人，大概率就是能一起走四年的人。", "keyPoints": [ "大一开学即启动招新，持续开放报名通道，越早越好", "四轮依次为演讲考核、寒假个人技术考核、大一下组队技术考核和终面", "面试官出题并提供学习资源，考核过程就是一次技术入门", "高门槛能筛选出更珍惜机会的人，但前提是有足够的报名基数", "中途纳新重点考察文化融合、创业意愿与家庭态度" ], "useWhen": [ "制定新一届招新方案", "设计考核题目与配套学习资料", "评估候选人是否适合联合创始团队" ], "workflow": [ "提前预告招新宣讲会，开放线上报名通道", "第一轮演讲考核，观察表达、感染力与创业意愿", "寒假个人技术考核，验证自学能力与投入度", "大一下组队技术考核，预留约一个月完成一个成品", "终面全面了解品性、创业意愿与家庭支持度", "最晚大一下完成全部考核，公示新成员并进入培养" ], "evidence": [ "首届负责人靠一场班内演讲，全班 32 人有 28 人报名", "宝典建议最晚大一下完成全部考核，以便立刻投入学习与项目", "书明确要求技术考核由面试官出题并提供学习资源" ], "limits": [ "考核节奏需按校历与专业课程灵活调整", "高门槛筛选依赖报名基数，宣讲与宣传不能省", "家庭态度属于个人隐私，询问应尊重边界并保密" ], "sourceBasis": [ "《穷学生宝典（第一版）》第一部分 · 关于团队招新" ], "tags": [ "招新", "四轮考核", "演讲", "技术考核", "中途纳新" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "featuredRank": 1, "featuredReason": "招新决定团队未来四年的下限：四轮考核把筛选、技术入门和归属感合并成一套流程，是新生理解团队的第一课。", "publicVersion": "sha256:94882f3ab0eddc5a92e21a4988f33e700c711fce873c188c360ed1483beb257c", "readingPriority": "P0", "relatedProjects": [ { "projectId": "aaaw-project-smart-gym", "basis": "项目讲解 lecture-gym-recruit（V10，知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-learn-build", "title": "学技术做项目：大学四年路径", "domain": "新生必修", "summary": "大一大二学技术、大二试校内项目、大三大四承接校外业务，配合三阶段技术分工，把四年排成一条成长曲线。", "plainLanguage": "先靠视频和文档把技术学起来，再用校内项目练手，最后靠校外业务挣钱；每一步都在为毕业前的公司做积累。", "keyPoints": [ "大一大二以学习技术为主，建学习文档并逐届更新传承", "大二开始做校内项目练运营，不追求盈利而重经验", "大三大四承接校外业务，以实战打磨团队并积累资金", "技术分工从市场组加技术组起步，逐步分化产品、测试与研发", "按市场需求定技术方向，不盲目深钻单一技术" ], "useWhen": [ "给新生排学习计划", "决定团队当前阶段该做什么", "评估成员学习方向与分工" ], "workflow": [ "建立技术学习文档并收集整理学习资料", "成员按前端、后端、UI 明确分工与学习目标", "大二选择一个校内方向做小项目并复盘", "大三大四开始承接外包业务并规范交付", "接触技术入股类合作时先明确股权与任务分配", "每学期复盘技术方向是否符合市场需求" ], "evidence": [ "宝典按年级给出学技术、做校内项目、承接校外业务的节奏", "书给出市场组技术组到研发测试的三阶段分工框架", "书强调技术方向要跟着市场调整并逐届传承学习资料" ], "limits": [ "节奏是建议而非硬性校规，需结合学业与成员实际", "校内项目涉及同学数据时注意隐私边界", "技术入股合作需书面约定，避免口头承诺" ], "sourceBasis": [ "《穷学生宝典（第一版）》第一部分 · 关于工作内容" ], "tags": [ "学技术", "校内项目", "外包", "技术分工", "成长路径" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "featuredRank": 3, "featuredReason": "新生的四年不能走一步看一步：先把技术学扎实，再靠项目练手、靠业务挣钱，这条路径直接决定毕业前能积累什么。", "publicVersion": "sha256:e73cd00ce358d8140e6ec8dc19fddc4816fa08994bb0e76fde95972c42418f23", "readingPriority": "P0", "relatedProjects": [ { "projectId": "aaaw-project-stream-recorder", "basis": "项目讲解 lecture-stream-learning（V10，知识层证据）", "evidenceLevel": "distilled" }, { "projectId": "teach-campus-ride-execution", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-office", "title": "办公室：场地生死线与办公规定", "domain": "新生必修", "summary": "优先争取校内免费或低租金场地，用开放式办公和成文规定维持工作状态，并让办公室在两届之间可持续传承。", "plainLanguage": "办公室就像蜗牛的壳。有固定场地，团队才能像企业一样每天运转；没有场地，再好的团队也大概率散伙。", "keyPoints": [ "固定办公场地是决定团队生死的基础设施，优先争取校内资源", "校外租房成本高，一年租金加开销可能接近三万，难以长期承受", "开放式办公让所有人的工作状态透明，禁止在办公室玩游戏、刷视频", "统一荣誉墙、本子、PPT 模板等视觉元素，文化建设包括物理环境", "两届团队同屋半年再分开，利于上一届言传身教；预留租金应对回收风险" ], "useWhen": [ "申请或交接办公场地", "制定办公室管理规定", "评估团队办公可持续性" ], "workflow": [ "先向创业学院、实验室或孵化中心申请校内场地", "谈不下再考虑与社团共用临时落脚点", "制定并张贴办公室规定，安排定期大扫除", "用考勤和开放办公维持工作状态", "两届同屋半年完成文化传递后按需分开", "与老师保持沟通并预留校外租金预案" ], "evidence": [ "宝典把办公场地列为决定团队生死的重要因素", "书给出三个场地途径：创业学院、学院实验室、校外孵化器", "书要求统一办公室视觉元素并禁止与工作无关的行为" ], "limits": [ "各校场地政策不同，以本校实际资源为准", "租金估算是书中的历史数据，需按当地行情复核", "共用办公室是过渡方案，不应长期替代独立场地" ], "sourceBasis": [ "《穷学生宝典（第一版）》第一部分 · 关于办公室" ], "tags": [ "办公室", "场地", "办公规定", "开放办公", "可持续" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "featuredRank": 4, "featuredReason": "场地是团队能否像企业一样运转的底线。新生第一天就该明白为什么坚持到办公室上班，而不是在宿舍远程凑合。", "publicVersion": "sha256:596507a5dddedea963c97786ee75e987ae18083f40d84fca12f164337755b35e", "readingPriority": "P0", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-oath-fund", "title": "成立仪式与100元创业基金", "domain": "新生必修", "summary": "以宣读誓词和每人缴纳 100 元启动资金开启一届团队，把共同创业的承诺和资金规则在第一天就讲清楚。", "plainLanguage": "成立仪式不是走形式。一句誓词、每人一百元启动资金，把“我们是共同创业者”变成所有人都要兑现的承诺。", "keyPoints": [ "新一届团队成立时全体成员宣读誓词，明确目标与核心价值观", "每人缴纳 100 元存入团队账户，作为本届启动资金", "成员中途离开不带走任何创业资金，制度提前讲清楚", "仪式感把价值观、目标和归属感一次性传递给新成员" ], "useWhen": [ "筹办新一届成立仪式", "设计团队初始资金规则", "向新成员解释制度含义" ], "workflow": [ "确定成立仪式时间与流程", "全体起立宣读誓词", "新成员缴纳 100 元创业基金并存入团队独立账户", "登记资金归属与使用规则", "向成员讲清离开不带走资金的约定", "把仪式照片与名单沉淀为团队记忆" ], "evidence": [ "宝典附有完整宣誓誓词，以毕业前成立可持续经营的公司为目标", "书规定 100 元启动资金存入本届团队账户", "书明确成员中途离开不带走包括启动资金在内的任何创业资金" ], "limits": [ "金额是象征性的启动资金，不能替代正式财务管理", "誓词表述可在不改变核心目标的前提下按届微调", "仪式材料属于内部资料，公开展示前需去敏" ], "sourceBasis": [ "《穷学生宝典（第一版）》第一部分 · 关于成立仪式" ], "tags": [ "成立仪式", "宣誓", "创业基金", "团队账户" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "featuredRank": 5, "featuredReason": "一百块钱买不来项目，但能买来一个郑重的开始：宣誓和共同出资让新成员第一次把团队目标当成自己的承诺。", "publicVersion": "sha256:963085303d17e028db598a2646c1da5ed57964788a402ea38e4a3f9303598b02", "readingPriority": "P0", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-street-canvas", "title": "扫街获客：主动出击的笨办法", "domain": "骨干运营", "summary": "用客户聚集地、同行合作、人脉推荐和扫街陌拜组合获客，靠模拟训练和分片执行把最难的主动出击变成日常训练。", "plainLanguage": "没有客户就一间一间办公室去敲。扫街最难的不是被拒绝，而是出发前那一周的准备和坚持走完的执行力。", "keyPoints": [ "获客渠道包括客户聚集地、同行合作、人脉推荐与扫街陌拜", "扫街前先做一周一对一模拟训练，预演被拒绝的场景", "去敏案例：团队为客户扫描两麻袋产品册、上架 2000 多个 SKU", "台风天打湿鞋裤仍坚持完成任务，把吃苦当训练", "被拒绝和驱赶很常见，应视为心理素质训练的机会" ], "useWhen": [ "团队早期寻找第一批客户", "新人第一次陌拜前的训练", "复盘获客转化低的原因" ], "workflow": [ "梳理目标区域与潜在客户名单", "准备一分钟说清团队能做什么的开场", "用一周做一对一模拟演练与话术打磨", "两人一组分片扫街并记录每家反馈", "拿到意向后按需求登记、方案、报价推进", "复盘转化率与话术，把经验写回团队知识库" ], "evidence": [ "某届团队在正式扫街前用一周做一对一模拟训练", "首个扫街客户来自玻璃钢厂老板的网页需求，团队背回两麻袋产品册完成扫描上架", "宝典把扫街列为最常见也最能锻炼胆量的获客方式" ], "limits": [ "案例细节已去敏，不代表可复制的收入水平", "扫街需遵守楼宇与园区管理规定", "陌拜话术要真实，不得夸大团队能力" ], "sourceBasis": [ "《穷学生宝典（第一版）》第一部分 · 关于拓展业务" ], "tags": [ "扫街", "获客", "陌拜", "外包", "心理素质" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:b9be8139cb8bc5f4d9eec422f48488e83c18fec950a06102a220cc29fb083ecc", "readingPriority": "P1", "relatedProjects": [ { "projectId": "teach-street-canvas-glass", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-meeting-sop", "title": "例会与例行工作 SOP", "domain": "骨干运营", "summary": "用日会、周会、月会分层掌握经营节奏，为每项例行工作建立含时间、流程、标准、执行人的 SOP，把靠自觉换成靠制度。", "plainLanguage": "会议频率决定团队反应速度，SOP 决定例行工作不会被人遗忘。两者都是把“靠自觉”换成“靠制度”。", "keyPoints": [ "日早会看数据、周例会定计划、月度会复盘经营", "开会频率决定调整战术的节奏，例会不能断", "例会包含汇报、研讨、经营播报与计划四类内容", "例行工作要建立 SOP：时间、流程、标准、执行人四要素", "SOP 需要持续砍掉冗余并迭代，不是定一次就完结" ], "useWhen": [ "搭建团队会议体系", "安排每周重复性任务", "复盘例行工作总被遗忘的问题" ], "workflow": [ "固定每日早会时间并在十五分钟内结束", "每周例会总结上周并定下周计划", "每月做一次经营数据复盘", "为每项例行工作写出时间、流程、标准与执行人", "指定检查人验收执行质量", "定期评审 SOP，砍掉无效步骤" ], "evidence": [ "宝典给出日例会、周管理研讨会、月度经营会议的完整时间表", "书用会议室清洁的例子说明 SOP 四要素", "书强调例行工作是公司正在创造价值的部分" ], "limits": [ "会议模板需按团队规模裁剪，避免形式主义", "SOP 文档属于内部资料，公开前需去敏", "例会数据涉及经营信息，不进入公开层" ], "sourceBasis": [ "《穷学生宝典（第一版）》第三部分 · 关于例会以及例行工作" ], "tags": [ "例会", "SOP", "例行工作", "复盘" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:5a1eff95acef9fb9d76e1fbf3443ca0ec22ff5ba24a7babb684dceb5048de9fb", "readingPriority": "P1", "relatedProjects": [ { "projectId": "aaaw-project-wteam-up", "basis": "项目讲解 lecture-wteamup-sop（V10，知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-tech-inheritance", "title": "技术沉淀与传承", "domain": "骨干运营", "summary": "把技术学习资料、踩坑记录和可复用模块文档化并逐届更新，让每一届都能在上一届的基础上起步。", "plainLanguage": "技术不能只存在老成员脑子里。学习文档逐届更新、模块封装复用，下一届才能站在上一届的肩膀上起步。", "keyPoints": [ "老成员的技术经验要整理成文档传承给新成员", "上一届负责更新技术学习资料，下一届快速上手", "平时开发注重模块封装与积累，缩短后续项目周期", "技术学习方向跟着市场需求逐届调整", "毕业师兄在同盟内继续提供技术经验分享" ], "useWhen": [ "交接技术资料给下一届", "组织内部技术学习与考核", "评估团队技术积累是否可复用" ], "workflow": [ "由技术负责人定期整理学习资料与路线", "按市场变化更新学习清单并标注优先级", "开发中沉淀可复用模块并写使用说明", "定期内部考核或比赛检验学习效果", "交接时新团队实际跑通一个最小案例", "把踩坑记录写回文档形成闭环" ], "evidence": [ "宝典要求每一届团队更新迭代技术学习资料", "书提倡成员注意技术积累与模块封装", "书鼓励向其他高校团队请教并共享优质学习资源" ], "limits": [ "资料链接可能随时间失效，交接时需逐项验证", "技术选型需按当年市场重新评估", "涉及合作项目的技术资料注意保密边界" ], "sourceBasis": [ "《穷学生宝典（第一版）》第三部分 · 关于学习技术" ], "tags": [ "技术沉淀", "传承", "模块封装", "学习资料" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:4ca4eb23fe382774c3ee1fb5b1f5a08f0f894c523e1577b87de136187d173ba9", "readingPriority": "P1", "relatedProjects": [ { "projectId": "aaaw-project-smart-gym", "basis": "项目讲解 lecture-module-reuse（V10，知识层证据）", "evidenceLevel": "distilled" }, { "projectId": "aaaw-project-linen-iot", "basis": "项目讲解 lecture-module-reuse（V10，知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-finance-open", "title": "财务公开：独立账户与三张报表", "domain": "骨干运营", "summary": "团队账户与私人账户分开、会计出纳分设、定期公示三张报表，把财务透明变成创始团队之间的诚信制度。", "plainLanguage": "钱的事越透明，团队越团结。独立账户、定期公示财报、说清每一块钱花在哪，是创始团队之间的诚信底线。", "keyPoints": [ "团队开设独立账户并与私人账户严格分开", "会计与出纳尽量分设，形成互相监督", "定期向全体成员公开财报是诚信问题", "负责人要看懂资产负债表、利润表和现金流量表", "清楚每一块钱的去向，才知道成本该省在哪里" ], "useWhen": [ "建立团队财务制度", "准备月度经营汇报", "向成员解释资金使用情况" ], "workflow": [ "开设团队独立账户并登记用途", "指定会计与出纳人选并明确职责", "按月整理三张报表并全员公示", "逐项核对大额支出与凭证", "用财报数据判断经营状况并调整策略", "换届或注册公司时完成账目交接" ], "evidence": [ "宝典要求团队账户与私人账户分开，会计出纳分设", "书把定期公开财报列为负责人的诚信义务", "书强调不重视财报是企业破产的原因之一" ], "limits": [ "报表模板是内部管理工具，不构成会计或法律意见", "金额与经营数据属于敏感信息，不进入公开层", "涉及税务与合规问题应咨询专业人士" ], "sourceBasis": [ "《穷学生宝典（第一版）》第三部分 · 关于定期公开财务报表" ], "tags": [ "财务", "独立账户", "财报", "透明" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:a1bc7a7cb285599298db90e50028db74448734681e4c3103ffd8a5b69226c424", "readingPriority": "P1", "relatedProjects": [ { "projectId": "prof-finance-domain", "basis": "V13 项目档案实体建立（prof-finance-domain），兑现 P0 pending 线索（知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-market-nose", "title": "市场嗅觉与判断", "domain": "负责人必修", "summary": "团队方向靠负责人的市场嗅觉与判断：多观察、懂请教、接触资本，再用小成本快速试错把判断变成结论。", "plainLanguage": "团队方向靠负责人的市场嗅觉。嗅觉不是天赋玄学，而是靠多观察、多请教、小成本快速试错练出来的判断力。", "keyPoints": [ "市场嗅觉决定发现机会的灵敏度，判断决定做什么、何时做、谁来做", "从身边商业活动开始培养商业意识与分析习惯", "谦虚请教他人，把会友当作获取市场信息的方式", "与资本保持接触，但警惕人人都看好的红海机会", "新项目用小规模快速试错验证，失败多数也要有一个成功", "好生意的三个条件：有利润、可持续、有复利" ], "useWhen": [ "寻找下一个项目方向", "评估一个机会是否值得投入", "安排试错的节奏与预算" ], "workflow": [ "持续记录行业观察与热点线索", "带着初步判断请教行业内的人并综合意见", "评估市场规模、痛点与自身匹配度", "用最小成本搭建验证并设定判断指标", "按数据决定加注或放弃", "复盘每次试错并更新机会清单" ], "evidence": [ "宝典把团队方向明确归因于负责人的市场嗅觉与判断", "书给出多观察、懂请教、接触资本三条培养建议", "某届团队曾同时测试二十多个方向，低成本快速迭代" ], "limits": [ "案例为去敏转述，不构成投资或商业建议", "试错不等于盲目铺摊，必须有止损线", "趋势判断需按当前时间重新校准" ], "sourceBasis": [ "《穷学生宝典（第一版）》第二部分 · 关于市场嗅觉与判断" ], "tags": [ "市场嗅觉", "试错", "机会判断", "好生意" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:8d5fd8be3e3ad7d8aac4c275ffb4dc85c3b8d3c78ff882f872025b0ba37e9b87", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "pending", "projectLinkNote": "知识层存在真实资料域线索（lecture:lecture-archive-focus），但该资料域尚未建立项目实体，待原始档案核验后补充关联", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-equity-dream", "title": "股权分配：分股份就是分梦想", "domain": "负责人必修", "summary": "避免平均分与一股独大，把股份分给长期同行者，注册前锁定退出机制与期权池，让股权结构服务于公司长期目标。", "plainLanguage": "股份是长期价值的载体。分给长期同行的人、定了就不乱改、离开按约定退出，才算把梦想分明白。", "keyPoints": [ "避免三人平分或一股独大两类极端结构", "股份分给愿意长期留在公司创造价值的人", "顾问式零星贡献不宜占股", "中途硬改股权结构容易引发矛盾，定了就保持稳定", "注册公司前约定退出机制：约定期限内离开不带走股份", "设期权池吸收未来优秀成员，通常由负责人代持但无决定权" ], "useWhen": [ "注册公司前设计股权结构", "讨论新成员或顾问的股份诉求", "处理股东退出的预案" ], "workflow": [ "明确公司长期目标与梦想规模", "按长期投入意愿筛选股东名单", "设计避免平分与独大的股权比例", "签署含退出机制与一致行动约定的协议", "预留期权池并明确代持与使用规则", "把股权文件与决议归档并逐届交接" ], "evidence": [ "宝典用投资人与团结两个视角分析平分与一股独大的问题", "书强调分股份就是分梦想，分给长期同行者", "书建议约定期限内离开不带走股份并提前签署协议" ], "limits": [ "书中结构是经验性建议，不构成法律意见", "涉及公司法与税务应咨询专业人士", "具体比例需结合团队实际协商确定" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于股权分配" ], "tags": [ "股权", "退出机制", "期权池", "创始人协议" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:03b12e9b37205d6b1cb4dd8a777dc5031b6f1499b1e9251dff51eaa633ce4831", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-succession", "title": "传承下一届：找头狼与不长臂管理", "domain": "负责人必修", "summary": "提前物色能独立带团队的下一届负责人，用技术、文化、人脉三条线完成交接，然后忍住不干涉下一届的决策。", "plainLanguage": "传承的关键是选对人，不是培养下属。找到能独立带团队的下一届负责人，然后把资源交出去，忍住不插手。", "keyPoints": [ "大二开学就开始物色下一届负责人", "选拔标准是能否独立组建团队，而不是当自己的下属", "技术、文化、人脉三条传承线都要交接", "师兄不做长臂管理，不干涉下一届决策", "舍得把校内资源交给下一届，鼓励他们面向校外市场", "每年借酒会与研讨会完成跨届深度交流" ], "useWhen": [ "启动下一届负责人选拔", "规划换届交接清单", "处理师兄与在校团队的边界" ], "workflow": [ "在日常相处中物色有创业属性的低年级学生", "以独立带团队为标准评估候选人头狼", "交接技术文档、制度文本与人脉名单", "安排同屋或共事期完成言传身教", "换届后转为顾问角色，不参与日常决策", "通过酒会与研讨会保持跨届联系" ], "evidence": [ "宝典建议大二一开学就物色下一届负责人", "书明确传承招新不是招募下属，80 分也可以找 120 分的人", "书要求师兄不长臂管理，在技术与业务上提供帮助为主" ], "limits": [ "选拔判断带主观性，需多届交叉验证", "传承断层无法完全避免，需以文字制度降低风险", "人脉交接应尊重双方意愿，不做强制安排" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于传承下一届" ], "tags": [ "传承", "换届", "头狼", "长臂管理", "人脉交接" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:2a104012e91dc72217b8c5d2061ec16f5009aa61fe22739b02c62518a7e47c4e", "readingPriority": "P2", "relatedProjects": [ { "projectId": "prof-knowledge-hub", "basis": "V13 项目档案实体建立（prof-knowledge-hub），兑现 P0 pending 线索（知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-removal", "title": "淘汰成员：原则与边界", "domain": "负责人必修", "summary": "价值观问题零容忍、状态问题给机会、早期由负责人亲自劝退、成熟期用制度淘汰，淘汰后做好公示与善后。", "plainLanguage": "淘汰不是为了排除异己，而是保护团队的前进方向。价值观问题零容忍，状态问题给机会，动手的人永远是负责人本人。", "keyPoints": [ "价值观出问题（诚信、受贿、挪用）立刻淘汰，不容忍", "阶段性惰怠先私下面谈并给调整机会", "早期淘汰由负责人亲自劝退，绝不用投票羞辱人", "成熟团队用制度淘汰，如 271 原则与末位机制", "淘汰后要公开说明原因并做好情绪疏导与交接", "选择时谨慎，认定后不轻易放弃长期同行者" ], "useWhen": [ "处理成员违反制度或长期低状态", "设计团队淘汰制度", "复盘一次艰难的人员决定" ], "workflow": [ "先判断问题属于价值观还是阶段性状态", "价值观问题立即启动淘汰流程", "状态问题私下面谈并约定观察期", "由负责人亲自面谈劝退，照顾情绪", "公开说明原因并完成工作交接", "疏导成员情绪并评估是否纳新补充" ], "evidence": [ "宝典按价值观、惰怠、早期与成熟期分别给出淘汰原则", "书明确反对用投票方式淘汰成员", "书提醒淘汰成员后负责人需公开宣布并做好善后" ], "limits": [ "淘汰决定涉及个人权益，流程应留存记录", "涉及股权的退出按协议处理，不与劝退混谈", "书中案例已去敏，不应指向具体个人" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于淘汰成员" ], "tags": [ "淘汰", "价值观", "劝退", "制度" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:1eb817d270905b1224e3dbd7e09e8f036567b7f8d53fdb92bc047519a2477077", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-wteam-overview", "title": "网维体系：梦想、坚韧、传承", "domain": "新生必修", "summary": "一分钟理解网维（WTEAM）是什么：以毕业前成立公司为目标的学生技术创业体系，靠上一届带下一届把经验变成制度。", "plainLanguage": "网维不是社团也不是实验室：它是一群用大学四年真实创业的人，梦想、坚韧、传承三个词就是这套体系的骨架。", "keyPoints": [ "目标：毕业前成立一家可持续经营的公司，并逐步发展壮大", "核心价值观：梦想、坚韧、传承", "不是社团（不盈利导向）、不是科研团队（不以创业为目的）、不是临时项目组", "上一届帮下一届是回馈机制，经验通过文字与制度沉淀", "网维同盟连接全国高校团队，提供年度研讨与孵化资源" ], "useWhen": [ "新成员第一次了解团队定位", "向老师、嘉宾或合作方介绍网维", "区分网维与校内其他组织的差异" ], "workflow": [ "读导言理解为什么大学是创业黄金期", "记住目标与三个核心价值观", "分清网维与社团、科研团队、项目制团队的区别", "了解同盟的研讨会与孵化支持", "进入「最有价值」模块从 P0 卡开始阅读" ], "evidence": [ "宝典导言与「网维团队的故事」章节", "2018 年 11 位负责人用两天两夜讨论 103 个话题形成本书", "同盟自 2019 年起在全国 60 多所高校帮助建立首届团队" ], "limits": [ "各校团队具体制度以本校文本为准", "书中数据为写作时点口径，引用需注明", "涉及具体人物的段落已去敏为角色表述" ], "sourceBasis": [ "《穷学生宝典（第一版）》导言 · 网维团队的故事" ], "tags": [ "网维体系", "核心价值观", "传承", "新生必读" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-31", "readingPriority": "P0", "publicVersion": "sha256:2036f33f93525d5d08e13e9518df906bb2644a011ba9cc27d04b009326cc969d", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-domain-governance", "title": "创新团队年度治理闭环", "domain": "团队治理与申报", "summary": "把申报、任务书、年度计划、过程记录、成果验收和下一年度计划连成一个可检查的管理闭环。", "plainLanguage": "团队不是提交一次申报书就结束，而是每年都要说明目标、留下过程证据、接受验收，再决定是否继续建设。", "keyPoints": [ "立项后及时签订任务书并提交年度计划", "过程记录册是检查进度和评价成果的重要依据", "验收材料必须同时包含成果与过程支撑", "政策、成果口径和时间节点须按当年文件复核" ], "useWhen": [ "准备创新团队申报或续建", "制定年度计划和月度复盘", "整理验收材料与成果证据" ], "workflow": [ "确认当年通知与申报条件", "定义成员分工、研究目标和预算", "提交申报书并完成评审", "立项后签任务书和年度计划", "持续记录研究进展与成员变动", "按年度提交成果、过程册和下一年度计划" ], "evidence": [ "2023 年管理办法明确校院两级管理与年度申报", "办法要求团队建立过程记录册", "验收采用基础要求加量化成果的动态管理" ], "limits": [ "制度材料属于历史版本，不能替代当年通知", "公开卡片不展示成员名单、联系方式和经费明细", "成果达标不等于网站已独立核验真实性" ], "sourceBasis": [ "广东海洋大学学生创新团队管理办法 2023", "学生创新团队申报书与年度验收附件目录" ], "tags": [ "立项", "过程管理", "年度验收", "证据闭环" ], "evidenceLevel": "document", "sourceYear": 2023, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:798095efaf54abb96f364772ba2b1b659533d6bb6bfd1dcd801ff2ed9691ad13", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "teach-gitlab-onboarding", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-domain-evidence", "title": "团队成果证据链", "domain": "团队成果与宣传", "summary": "把成果主张、原始证明、项目过程和公开素材分层管理，避免宣传材料与事实证据混为一谈。", "plainLanguage": "先回答这件事有什么原始证据，再决定能不能对外讲、应该怎么讲，而不是只收集漂亮图片。", "keyPoints": [ "每条成果主张都对应可定位的原始证明", "团队级成果和个人级成果分开", "过程照片不能替代奖项或知识产权证明", "公开副本必须去除人员与凭据数据" ], "useWhen": [ "制作团队介绍或答辩材料", "核验奖项、论文、专利和软著", "交接历届成果档案" ], "workflow": [ "登记成果主张和责任人", "定位证书、文件或官方页面", "核对完成单位、时间和成果角色", "建立去敏公开副本", "在宣传材料中标注证据等级", "定期复核失效链接和待确认项" ], "evidence": [ "资料包含团队介绍、成果采集表、证书和答辩材料", "同一成果存在宣传副本与证明材料两种用途", "部分历史文件存在重复版本，需要保留来源关系" ], "limits": [ "目录存在不等于成果真实有效", "文件时间不能直接当作成果发生时间", "涉及身份证明、证书编号和人员信息的原件不得公开" ], "sourceBasis": [ "学生创新团队年度成果数据采集表", "团队成果答辩材料", "创新团队介绍与佐证材料目录" ], "tags": [ "证据链", "成果核验", "宣传", "去敏" ], "evidenceLevel": "catalog", "sourceYear": 2023, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:7de414f20191e27a36e1218cd1d12d600792d5af3150e7022586db88d4ff1a5a", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "teach-juice-shop-security", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-domain-project-delivery", "title": "软件项目交付六层模型", "domain": "项目研发与交付", "summary": "用需求、协议、源码、构建物、部署配置和验收证据六层结构管理项目，避免把一个压缩包误当成完整交付。", "plainLanguage": "能运行的成品、能继续开发的源码、能复现上线的配置和能证明交付的验收记录，是四件不同的事。", "keyPoints": [ "需求和变更先于实现", "源码与构建物保持版本对应", "部署配置和凭据必须独立受控", "验收要验证真实页面与关键流程" ], "useWhen": [ "接手历史项目", "准备客户交付", "判断旧项目是否还能维护", "整理项目归档" ], "workflow": [ "确认需求范围和验收标准", "登记源码仓库与版本", "生成可复现的构建产物", "分离环境配置和秘密信息", "记录部署步骤与回滚点", "用真实入口完成验收并归档证据" ], "evidence": [ "项目区同时出现需求文档、源码压缩包、构建目录和后端制品", "部分项目只有构建物，不能证明源码可维护", "部分归档混入数据库与运维凭据，需要隔离" ], "limits": [ "存在源码不代表依赖完整或可构建", "存在部署包不代表当前服务器仍可用", "未经许可证和隐私复核不得对外共享源码" ], "sourceBasis": [ "项目研发与交付目录清单", "码流收录系统需求说明", "多个软件项目构建与部署归档" ], "tags": [ "需求", "源码", "构建", "部署", "验收" ], "evidenceLevel": "catalog", "sourceYear": 2024, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:c881462f2fc30ac4c3cfc9a6a50e67c86e2be80b09ea5950fcb88acf1ba606f5", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "teach-cal-booking", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" }, { "projectId": "teach-juice-shop-security", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" }, { "projectId": "teach-campus-ride-execution", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-domain-learning", "title": "竞赛与大创材料学习法", "domain": "竞赛与学习", "summary": "把规则、模板、往届案例、自己的初稿和复盘证据按顺序使用，避免照抄旧材料。", "plainLanguage": "旧案例用来理解结构和评分逻辑，不是拿来替代当年规则，更不能把别人的项目内容换个名字直接提交。", "keyPoints": [ "先读当年通知和评分要求", "模板用于检查结构完整性", "案例用于比较论证方法", "最终材料必须回到自己的问题与证据" ], "useWhen": [ "准备竞赛计划书", "申报大学生创新训练项目", "训练答辩和复盘能力" ], "workflow": [ "锁定当年官方规则", "拆解模板字段和评分点", "选取一份同类案例做结构标注", "建立自己的问题证据表", "完成初稿并逐项反证", "保留修改记录和最终验收结果" ], "evidence": [ "资料同时包含参考模板、申报流程和多个往届案例", "蓝桥杯题库与课程设计材料可支持专项练习", "部分财务指南属于历史流程，需单独复核" ], "limits": [ "历史案例不代表当年政策", "案例质量未经统一评价", "公开知识卡不提供原始参赛材料下载" ], "sourceBasis": [ "大创申报指南", "互联网加项目计划书参考模板", "蓝桥杯与课程设计资料目录" ], "tags": [ "竞赛", "大创", "案例分析", "复盘" ], "evidenceLevel": "document", "sourceYear": 2025, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:0b1c7ace65f66c74342f68e819b03e5ce7c718a8d900f512a575abc0dfac8dd1", "lastReviewedAt": "2026-10-28", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-project-smart-gym", "title": "高校体育馆预约系统业务模型", "domain": "项目研发与交付", "summary": "围绕微信登录、场地与时段、订单支付、入场码、退款和后台配置形成的预约系统业务闭环。", "plainLanguage": "用户看到的是选场地和付款，系统真正难点是保证同一时段不重复售卖、订单状态一致，并让后台配置准确影响前台。", "keyPoints": [ "微信身份与用户账户绑定", "场地日期时段和收费规则", "订单支付入场码与退款状态", "门店场地储值卡和管理员配置" ], "useWhen": [ "设计场馆或会议室预约产品", "梳理订单状态机", "评审小程序与后台边界" ], "workflow": [ "后台配置门店、场地和开放时段", "用户登录并选择日期与场次", "系统校验库存并生成待支付订单", "支付成功后生成可核验入场凭证", "用户查看订单或申请退款", "后台处理订单并复核场地利用率" ], "evidence": [ "软件说明书记载微信登录与订场流程", "说明书记载按日期时段收费和免费场设置", "说明书记载支付、入场码、订单查询、退款与后台场地管理" ], "limits": [ "说明书描述功能，不等于当前线上系统仍可用", "支付、退款和并发占位未做代码级验证", "人员信息和申请材料保留在受限区" ], "sourceBasis": [ "高校体育馆预约管理系统软件说明书", "高校体育馆预约管理系统归档目录" ], "tags": [ "预约系统", "订单状态", "微信小程序", "运营后台" ], "evidenceLevel": "document", "sourceYear": 2024, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:258fd91b53e707477d50f84b319cb9ddffdd987e652cc4500b1b31402e3e0b8e", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "teach-cal-booking", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" }, { "projectId": "prof-smart-gym", "basis": "V13 项目档案建立（知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "reference", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-project-linen-iot", "title": "多端物联系统接管清单", "domain": "项目研发与交付", "summary": "设备端、用户端、管理端和后台服务分包归档时，应先建立系统边界与接口地图，再判断是否可维护。", "plainLanguage": "四个代码包不等于四套独立系统；它们通常共享账户、订单和设备状态，接手前必须先弄清谁调用谁。", "keyPoints": [ "识别设备端用户端管理端和服务端", "建立接口与数据所有权地图", "核对版本和环境依赖", "先做最小链路验证再改业务" ], "useWhen": [ "接手多端物联网项目", "整理多个历史代码包", "评估系统能否继续迭代" ], "workflow": [ "为每个包确认角色和启动入口", "登记语言框架和依赖版本", "梳理账户订单设备三类核心实体", "定位接口地址与鉴权方式", "在隔离环境跑通一条最小业务链", "形成缺失项和风险清单" ], "evidence": [ "归档中存在设备端、用户端、管理端和后台四类独立代码包", "文件名可以支持多端边界判断", "当前尚无经复核的业务需求文档" ], "limits": [ "目录证据不足以确认具体业务功能", "数据库与接口配置不得直接上线复用", "未完成构建和运行验证前保持目录核对等级" ], "sourceBasis": [ "恒峰布草物联管理系统四端归档目录" ], "tags": [ "物联网", "多端", "接口地图", "接管" ], "evidenceLevel": "catalog", "sourceYear": 2024, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:25799c9cfc1e70a35362db58da99a5790885fff3a747b1c365f2bc9306021cc2", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "teach-thingsboard-iot", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" }, { "projectId": "prof-linen-iot", "basis": "V13 项目档案建立（知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "reference", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-project-stream-recorder", "title": "码流故障触发录制架构", "domain": "项目研发与交付", "summary": "以多路 TS over IP 持续录制为基础，通过分析仪错误计数触发带前置缓存的故障片段留存。", "plainLanguage": "系统平时持续接收电视传输流；分析仪发现错误后，录制系统不仅保存故障之后的数据，还要把故障前十到三十秒一起保留下来。", "keyPoints": [ "支持 UDP 或 RTP 的单播和组播", "分析仪提供错误类型和累计数量", "触发条件需要计算单位时间内的增量", "存储容量必须按码率保留天数和阵列利用率估算" ], "useWhen": [ "设计广播电视码流留证系统", "评审事件触发录制", "估算高码率长期存储" ], "workflow": [ "登记分析仪设备和接收端口", "持续采集码流并维护环形缓存", "周期查询错误计数并计算增量", "达到门限时固化前后故障片段", "记录任务日志报警和文件元数据", "按保留策略清理或迁移文件" ], "evidence": [ "需求明确单机一百路以上并行录制目标", "需求明确错误触发和十至三十秒缓存", "需求给出原始录制与转码录制的容量估算示例", "接口采用 HTTP 请求与结构化数据返回" ], "limits": [ "这里记录的是需求指标，不代表已经实现", "容量公式需按阵列可用容量和真实码率重新计算", "接口地址和设备网络信息不进入公开层" ], "sourceBasis": [ "码流收录系统功能需求说明 v1.2" ], "tags": [ "TS over IP", "故障触发", "环形缓存", "容量规划" ], "evidenceLevel": "document", "sourceYear": 2023, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:74a59896336ea8e798c018b3269ceb9070d2b56875866487669ea4e272b3ed8b", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "teach-ffmpeg-event-recording", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" }, { "projectId": "prof-stream-recorder", "basis": "V13 项目档案建立（知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "reference", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-project-wteam-up", "title": "历史部署包审计方法", "domain": "项目研发与交付", "summary": "面对只有大型压缩包或构建目录的旧项目，先做无执行审计，再决定是否解压、构建或恢复服务。", "plainLanguage": "旧部署包最危险的做法是直接运行。正确顺序是先看目录、哈希、配置痕迹和依赖，再放进隔离环境验证。", "keyPoints": [ "原件只读并计算哈希", "先列清单不执行文件", "识别构建物配置和秘密信息", "恢复前建立隔离环境和回滚点" ], "useWhen": [ "接手历史压缩包", "恢复没有文档的旧站点", "判断归档是否值得继续保留" ], "workflow": [ "复制工作副本并保留原件", "生成文件清单与类型统计", "扫描凭据数据库和可执行文件", "判断源码与构建物是否齐全", "在隔离环境做最小启动验证", "形成可恢复不可恢复与待确认结论" ], "evidence": [ "WTEAM-UP 当前主要以归档压缩包形式存在", "同类项目区可见构建物与部署配置混放现象", "现有目录不足以证明可复现部署" ], "limits": [ "未解包验证前不声明技术栈和功能", "不直接执行未知脚本或程序", "发现凭据后先轮换再继续恢复" ], "sourceBasis": [ "WTEAM-UP 历史归档目录", "软件项目归档目录清单" ], "tags": [ "部署", "归档审计", "隔离验证", "回滚" ], "evidenceLevel": "catalog", "sourceYear": 2023, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:22a99211f269686f91a19707eec8d62a0eaf7a1fcd3bd5936d76c15bb62a6cb8", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "prof-wteam-up", "basis": "V13 项目档案建立（知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "reference", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-practice-archive-security", "title": "项目归档敏感信息处置", "domain": "项目研发与交付", "summary": "项目说明、安装日志和运维记录可能混入真实服务器入口与登录凭据，不能因文件名看似业务方案就直接公开。", "plainLanguage": "先把文档当作可能泄密的运维记录检查，再把可以公开的业务知识单独重写；绝不能原样上传。", "keyPoints": [ "内容分类不能只依赖文件名", "发现凭据立即隔离并推动轮换", "公开知识必须重新表述而非简单删几行", "泄露风险与业务价值分开评估" ], "useWhen": [ "发布历史项目资料", "整理交接文档", "扫描网盘或代码仓库" ], "workflow": [ "只读扫描文档和压缩包清单", "识别地址账户令牌和私钥模式", "隔离原件并登记风险", "确认凭据是否仍有效并安排轮换", "从安全副本提取非敏感知识", "发布前再次执行敏感模式检查" ], "evidence": [ "代表性项目文档中出现与标题无关的服务器安装日志", "归档区还包含数据库和运维配置线索", "当前公开构建包含敏感模式扫描" ], "limits": [ "公开卡片不复述任何地址账户或密码", "仅删除敏感行不足以证明上下文安全", "凭据是否仍有效需要资产所有者确认" ], "sourceBasis": [ "软件项目归档安全复核记录", "公开内容敏感模式校验规则" ], "tags": [ "敏感信息", "凭据轮换", "发布审查", "去敏" ], "evidenceLevel": "verified", "sourceYear": 2026, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:8c3fc0f0432c184eb4dab5922da9f58dcc38f2a8b58b8049a46c0c545c44c615", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "teach-juice-shop-security", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "task", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-practice-newcomer-start", "title": "新生九十天上手路线", "domain": "团队治理与申报", "featuredRank": 2, "featuredReason": "把入队后的观察、训练、真实任务和独立交付排成九十天路线，避免新人只开会、只打杂或长期依赖学长代做。", "summary": "用了解团队、完成最小训练、参与真实项目、独立交付和复盘五个阶段，让新成员逐步承担责任。", "plainLanguage": "新人不需要一开始就接大项目，但必须尽快完成一个能被检查的小任务，并在九十天内证明自己能独立交付和复盘。", "keyPoints": [ "先理解团队规则、资料边界和成果口径", "训练任务必须有明确产物和验收标准", "学长提供指导但不替新人完成任务", "九十天结束形成能力证据和下一阶段计划" ], "useWhen": [ "新成员入队与试用期安排", "设计一轮考核和导师带教", "解决新人只打杂或无法独立的问题" ], "workflow": [ "第一个月熟悉制度、资料地图和安全边界", "完成一个可在一周内验收的基础训练任务", "第二个月加入真实项目并承担一个边界清楚的模块", "用需求、过程记录、成品和测试结果完成交付", "第三个月独立处理一次问题并向团队复盘", "根据证据确定继续培养方向和下一阶段目标" ], "evidence": [ "实验室制度强调低会议负担和新生独立完成工作", "制度提出保留少量项目供新人学习但不能依赖继承项目", "创新团队管理办法要求明确分工、过程记录和年度成果" ], "limits": [ "九十天是建议节奏，不是学校正式考核规定", "训练强度不得伤害健康、学业或正常休息", "能力评价应基于实际产物，不能只看在线时长" ], "sourceBasis": [ "网维创业团队实验室规章制度", "广东海洋大学学生创新团队管理办法 2023", "团队考核与验收资料目录" ], "tags": [ "新人培养", "九十天", "导师带教", "独立交付" ], "evidenceLevel": "document", "sourceYear": 2023, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:a537ad157b9f7d005f71d6a5dbc22e9f09d36ff9762c8f65185f1dfe1b63853b", "lastReviewedAt": "2026-10-28", "relatedProjects": [ { "projectId": "teach-gitlab-onboarding", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "task", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-practice-student-outsourcing", "title": "学生软件外包决策框架", "domain": "团队治理与申报", "summary": "用学习时间、需求质量、价格、返工边界、付款和长期价值判断一个外包项目是否值得接。", "plainLanguage": "能接不等于该接。先确认不会伤害学业和健康，再确认需求、价格、修改次数和付款方式都讲得清楚。", "keyPoints": [ "先算时间与机会成本", "报价必须覆盖沟通测试和返工", "用书面协议冻结范围与验收", "保留拒绝低价或不靠谱需求的权利" ], "useWhen": [ "团队评估新外包", "新人第一次接真实项目", "复盘延期低价或反复改需求的问题" ], "workflow": [ "判断课业与健康是否允许", "澄清需求交付物和验收口径", "估算开发沟通测试与维护成本", "约定里程碑修改次数和付款", "小范围验证后再全面开发", "交付后复盘收益风险与可沉淀知识" ], "evidence": [ "内部经验材料同时列出真实项目经验与时间健康风险", "材料强调了解行情和劳动价值", "材料建议通过详细协议控制反复修改" ], "limits": [ "经验材料不是法律意见", "涉及合同税务和知识产权时应咨询专业人士", "学生身份不能替代正式的项目管理与质量责任" ], "sourceBasis": [ "团队主营业务软件外包说明" ], "tags": [ "外包决策", "范围管理", "报价", "验收" ], "evidenceLevel": "document", "sourceYear": 2023, "visibility": "public", "contentStatus": "published", "publicVersion": "sha256:27ad27977f0e04772b0b7067aee1a8e8775123e567056e97cad3461dbb6432c8", "lastReviewedAt": "2026-10-28", "featuredRank": 6, "featuredReason": "让第一次接真实项目的新人先算学业、健康、范围、返工和付款风险，再判断项目值不值得做。", "relatedProjects": [ { "projectId": "teach-street-canvas-glass", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "task", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-speech-training", "title": "演讲内训：每周一次的公开表达", "domain": "骨干运营", "summary": "以每周一次、每人 15-20 分钟的固定演讲内训，把表达练成团队的基本功，并用提问评分让认知持续迭代。", "plainLanguage": "演讲是统一思想、打动客户和招新的基本功。它不靠天赋，靠每周一次的刻意练习和一场接一场的点评打磨。", "keyPoints": [ "每周固定用一个上午或下午，每人演讲 15-20 分钟，全员参加", "主题围绕创业、擅长领域或个人深度思考", "脱稿为主，PPT 只做提纲，眼神要像摇头风扇一样照顾全场", "听众从主题内容与演讲技巧两方面提问、点评并按 10 分制打分", "出现疲倦感时引入外部嘉宾、奖惩或暂停重启等新元素" ], "useWhen": [ "搭建团队内训体系", "准备招新演讲或客户提案前练兵", "复盘成员表达能力短板" ], "workflow": [ "演讲前三天确定主题并发放 A4 纸列提纲", "按固定频次轮流登台，未讲满时长也要站满", "听众按座位顺序提问与点评并打分", "负责人带头争取每次前三名", "A4 提纲回收归档，供重复使用", "定期更换形式防止倦怠" ], "evidence": [ "宝典把演讲列为四大内训最核心的制度", "书用一个煮黄豆也能讲得有人信的故事演示演讲的说服力", "书要求演讲后回收提纲由专人整理收纳" ], "limits": [ "评分是训练手段，不用于公开排名", "演讲内容涉及业务数据时注意去敏", "频率需与学业节奏平衡，避免形式化" ], "sourceBasis": [ "《穷学生宝典（第一版）》第三部分 · 关于演讲" ], "tags": [ "演讲", "内训", "表达", "点评评分" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:1d2784cbfc8f99739b0c467b443ca7f7180cd6a4e04f41a0d32e45ff7f9d86cb", "readingPriority": "P1", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-friend-visits", "title": "会友内训：把办公室变成人脉入口", "domain": "骨干运营", "summary": "每周轮流邀请老师、社团、客户和校友到办公室交流，锻炼对外表达的同时带来市场信息与合作机会。", "plainLanguage": "闭门写代码等不来机会。每周请一位客人来办公室喝茶聊天，既是待客训练，也是市场信息的入口。", "keyPoints": [ "每周一次，成员轮流负责邀约，可选一个下午", "对象包括老师、社团负责人、其他团队、客户与校友", "既介绍团队理念与业务，也认真听对方的故事与行业判断", "对方来一两个人时，团队两三人陪同即可，避免围堵感", "积累的校内人脉要在换届交接时传给下一届" ], "useWhen": [ "扩大校内影响力与人脉", "获取行业信息与潜在合作", "训练成员待客与表达能力" ], "workflow": [ "排出每周轮值邀约表", "确定对象并提前发出邀请", "准备团队介绍与当期话题", "接待交流并记录对方背景与要点", "会后整理有价值的线索并跟进", "换届前把人脉清单与关系交接给下一届" ], "evidence": [ "宝典将会友列为四大内训之一，明确频率与对象范围", "书指出会友让老师放心、让客户信任并带来转介绍", "书要求把人脉资源以会友方式介绍给下一届团队" ], "limits": [ "不强制全员出席，避免给客人压力", "涉及客户信息时注意保密", "频率按校历与考试周弹性调整" ], "sourceBasis": [ "《穷学生宝典（第一版）》第三部分 · 关于会友" ], "tags": [ "会友", "人脉", "内训", "校内影响力" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:c57aef3d7e8493482b39084cef9cf1fe0f6c7b34d9478de7f668796080143939", "readingPriority": "P1", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-self-criticism", "title": "自我批评会：对事不对人的复盘", "domain": "骨干运营", "summary": "每两月至半年一次的批评与自我批评会，负责人带头剖析自身问题，让团队把暴露缺点当成进步的正常路径。", "plainLanguage": "人容易看见别人的问题，看不见自己的。定期的自我批评会就是把这条人性缺口变成团队进步的通道。", "keyPoints": [ "每两月至半年一次，定在一个下午或晚上", "负责人先带头自我批评，再由成员补充，最后给出承诺与改进方案", "全员轮流做自我批评并接受他人批评", "氛围要严肃认真、语气诚恳，控制好度", "防止开成批斗会，不伤人、不翻旧账、不影响团结" ], "useWhen": [ "阶段性复盘团队协作问题", "处理反复出现的低效与摩擦", "训练成员接受反馈的心态" ], "workflow": [ "确定时间地点并提前说明规则", "负责人第一个做自我批评并示范分寸", "成员轮流发言，他人补充意见", "每人给出可检查的改进承诺", "记录问题与承诺并在下次会前回顾", "会后一对一安抚情绪较重的成员" ], "evidence": [ "宝典把自我批评列为四大内训之一，引用华为的自我批判文化", "书明确负责人带头、随后他人补充、最后自作承诺的流程", "书提醒避免过于严厉导致批斗化" ], "limits": [ "频次不宜过高，避免变成压力仪式", "涉及个人隐私的问题不强制公开", "批评意见应对事并留有记录" ], "sourceBasis": [ "《穷学生宝典（第一版）》第三部分 · 关于自我批评" ], "tags": [ "自我批评", "复盘", "内训", "反馈" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:6dca1a23d70ef68254a40b6f21cb48cce40c8d7c56f9d11259f19081aa39f310", "readingPriority": "P1", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-networking", "title": "建立人脉：先有价值，再谈圈子", "domain": "负责人必修", "summary": "人脉的本质是资源整合与主动链接：负责人要广泛结识、主动付出，并把自身实力当作进入更高圈层的入场券。", "plainLanguage": "混圈子混不进 higher 的局。你能带来什么价值，决定了谁愿意认识你；先把自己变强，人脉才会顺过来。", "keyPoints": [ "建立人脉的过程就是资源整合的过程", "团队早期要做主动链接别人的人，多付出、肯吃亏", "内向的负责人要有意识地训练表达，不让社交成为短板", "与优秀的人为伍的唯一方式是把自己变得同样优秀", "把会友、请教、合作都当作获取市场信息的渠道" ], "useWhen": [ "规划负责人的对外时间投入", "评估团队当前的资源缺口", "寻找合作与项目机会" ], "workflow": [ "列出当前需要的资源与对应的人群", "通过会友、行业活动、师兄网络主动结识", "交流时先了解对方需求，思考可以提供什么", "能合作就合作，合作前确认背景与为人", "定期维护关系节点并更新人脉清单", "把有价值的关系沉淀并传承给下一届" ], "evidence": [ "宝典专章讨论资源整合、主动链接与建立人脉的能力", "书强调没有足够的能力，跪着也进不了想进的圈子", "书建议把请教高人与链接外部世界作为快速进步的方式" ], "limits": [ "人脉经营需投入时间，不能挤占核心业务", "合作涉及利益时必须有书面约定", "对外的承诺以团队能力为上限，不夸大" ], "sourceBasis": [ "《穷学生宝典（第一版）》第二部分 · 关于建立人脉" ], "tags": [ "人脉", "资源整合", "主动链接", "合作" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:23cb74a6daa2366b136ba552758abf593c271e5b298dd2debe14a069124149dc", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-blueprint", "title": "描绘蓝图：可量化的目标进度条", "domain": "负责人必修", "summary": "把个人、家庭、国家、世界四个层次的动力都用足，把蓝图量化、拆解到每一天，并用进度条让团队看见希望。", "plainLanguage": "蓝图和画饼是同一件事的两种情绪。可量化、有路径、反复提起、拿结果验证的，才叫蓝图。", "keyPoints": [ "个人财富、家庭幸福、行业地位、改变世界四个目标都是动力", "蓝图必须可量化、清晰、可复述、可文字化", "把毕业前目标拆解到大一到大四，再细分到每季度每月每周每天", "设置完成目标的进度条，展示阶段性成果", "不用带负向情绪的词（画饼、灌鸡汤），多说我们要怎么做", "负责人内心动摇是团队的毁灭性打击，必须 100% 坚信" ], "useWhen": [ "制定团队年度与学期目标", "激励团队度过枯燥的外包期", "复盘目标是否偏离路径" ], "workflow": [ "确定毕业前的总目标并量化", "按学年学期拆解为阶段目标", "把当前阶段目标细化到每周动作", "建立可见的进度条或里程碑表", "每次拿到结果就公开更新进度并庆祝小胜", "定期复盘蓝图与现实的差距并调整路径" ], "evidence": [ "宝典给出四个层次目标的动力框架", "书里有团队拿到 3000 元尾款时以汽车轮子比喻进度让团队干劲十足", "书要求蓝图可量化可复述并设置进度条" ], "limits": [ "目标要随现实校准，避免为了激进数字损害健康与学业", "进度条是管理工具，不对外宣传未经核实的业绩", "短期未达标时优先调整路径而非降低信念" ], "sourceBasis": [ "《穷学生宝典（第一版）》第二部分 · 关于描绘蓝图" ], "tags": [ "蓝图", "目标拆解", "进度条", "愿景" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:8f0471c2d854f3007765d7b1399cbed009feb745a37eae0579552582f67e036e", "readingPriority": "P2", "relatedProjects": [ { "projectId": "teach-blueprint-progress", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-one-on-one", "title": "定期面谈：CEO 的管理利器", "domain": "负责人必修", "summary": "用每周一次的一对一面谈贯彻文化、加强信任、提前化解离开念头，把问题消灭在萌芽状态。", "plainLanguage": "成员提出离开时，心里已经挣扎了几个月。每周一小时的一对一，就是把这几个月的苗头提前接住。", "keyPoints": [ "面谈要占管理者大量时间，书建议每周与所有成员各谈一次", "在放松环境下了解工作、生活、问题与新想法", "同时推进工作：项目进展、新任务与正能量", "一对一是建立互信与公信力的主要通道", "发现认知不一致时当场对齐，不留到例会" ], "useWhen": [ "日常团队管理节奏安排", "成员状态出现波动时", "新人融入与文化传递" ], "workflow": [ "固定每周面谈时间表并覆盖全部成员", "以近况与感受开场，再谈工作", "记录关键问题、承诺与跟进事项", "对离开念头先回应过段时间再谈，给冷静期", "把面谈中发现的问题归类并推动解决", "月度复盘面谈覆盖率和悬而未决事项" ], "evidence": [ "宝典引用管理学观点与网维负责人经验，主张六成时间用于面谈也不为过", "书认为定期面谈做好就不会出现成员忽然离开", "书把一对一谈话称为最直接的企业文化建设方法" ], "limits": [ "面谈内容涉及隐私，记录需保密", "时长按团队规模裁剪，避免流于形式", "面谈不能替代制度与例会" ], "sourceBasis": [ "《穷学生宝典（第一版）》第二部分 · 关于定期面谈" ], "tags": [ "面谈", "一对一", "信任", "留人" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:7bcc648988f8f6371bf245eaa3e9c02e408693d79508e66067490079adf26c35", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-management-pyramid", "title": "管理能力：道谋断人阵行金字塔", "domain": "负责人必修", "summary": "用道、谋、断、人、阵、行六层金字塔理解管理，按团队规模选学适配的管理体系，一切为执行力服务。", "plainLanguage": "管理不是玄学：使命愿景是道，战略战术是谋，决断是断，用人育人是人，组织制度是阵，全都为了最后的执行力。", "keyPoints": [ "有效管理人才的能力才是企业核心竞争力", "金字塔六层：道（使命愿景价值观）、谋（战略战术）、断（决策）、人（人员）、阵（组织制度）、行（执行）", "百人以内推荐余世维式课程，千人以上再学稻盛和夫或华为体系", "管理体系不能生搬硬套，达不到规模就理解不了相应知识", "从十人到千人，管理策略要随阶段调整" ], "useWhen": [ "为负责人排管理学习计划", "诊断团队执行力问题的层级", "搭建组织制度与文化建设" ], "workflow": [ "用六层金字塔给团队现状打分", "找出最弱的一层作为本阶段重点", "选择与规模匹配的管理课程或书籍学习", "每季度把学到的方法落地为制度或动作", "在例会复盘执行效果", "随规模升级迭代管理体系" ], "evidence": [ "宝典系统介绍金字塔模型并注明源于通用电气等企业实践", "书给出按规模分层的书单建议（余世维、稻盛和夫、华为）", "书强调所有维度都为执行力服务" ], "limits": [ "书单是经验推荐，不是唯一路径", "管理知识需结合实践，避免纸上谈兵", "高压体系与高幸福感体系观点相悖，选型要一致" ], "sourceBasis": [ "《穷学生宝典（第一版）》第二部分 · 关于管理能力" ], "tags": [ "管理", "金字塔", "执行力", "管理体系" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:23146348efc9a219dd7b99800c6fbfd2bec1da19ff75e05e1d09ffaf7d6f7525", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-grow-managers", "title": "培养管理层：内部培养优先于空降", "domain": "负责人必修", "summary": "高管队伍尽量从内部培养，在管理理念上与成员达成共识；业务爆发期可空降补位，但要预期其流动性。", "plainLanguage": "年轻的 CEO 管不动空降高管是常态。从第一天就开始培养自己人，才是基业长青的正规打法。", "keyPoints": [ "大多数长青公司的高管队伍从内部培养", "从早期开始传授管理知识并定期深度探讨", "在管理理念和认知上与成员达成共识", "业务快速增长期可空降职业经理人补位", "空降高管通常不会留十年二十年，要提前做好接替准备" ], "useWhen": [ "规划管理岗继任与梯队", "考虑是否从外部引进高管", "安排骨干的管理训练" ], "workflow": [ "从核心成员中物色管理潜质者", "安排带小项目练管理与决策", "定期做一对一管理探讨并统一认知", "空降岗位明确过渡期与交接要求", "为每个关键岗位准备至少一名接班人", "复盘管理岗变动对团队的影响" ], "evidence": [ "宝典指出年轻 CEO 难以管理空降高管团队是普遍现象", "书建议从一开始就培养队伍并达成认知共识", "书提醒空降职业经理人几年后可能流向更好平台" ], "limits": [ "内部培养需要时间，业务空窗期需权衡", "空降与内部体系的融合需要缓冲设计", "本卡不构成人力资源操作指引" ], "sourceBasis": [ "《穷学生宝典（第一版）》第二部分 · 关于培养管理层" ], "tags": [ "管理层", "梯队", "内部培养", "空降" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:63a0aae82e8a71322c69a584fd63a99774e3c1248580c898294d6411b23850e3", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-departure", "title": "成员主动离开：识别、挽留与防连锁", "domain": "负责人必修", "summary": "区分客观离开与情绪离开，用冷静期与面谈挽留情绪型，用规定与低调处理防止连锁反应，并提前做人才储备。", "plainLanguage": "有人走不可怕，可怕的是一个人走带崩一群人。离开要私下沟通、低调处理，然后盯紧剩下人的状态。", "keyPoints": [ "离开分客观型（更好选择）与情绪型（阶段性不开心）", "情绪型离开先给半个月到一个月冷静期再谈", "大三迷茫期与毕业期是两个集中离开的时间点", "规定想离开先与负责人私下沟通，不得在团队内散播", "离开后低调处理、半个月内密切关注军心", "各岗位提前储备与多技能培养，防关键人流失" ], "useWhen": [ "处理成员提出的离开", "大三与毕业两个动荡期的预案", "复盘人才断层风险" ], "workflow": [ "先判断离开属于客观还是情绪", "情绪型给冷静期后再深度面谈", "用业务增长与蓝图回应经营疑虑", "按约定引导私下沟通，阻止负向蔓延", "低调公布并做好工作交接", "启动储备培养并复盘缺口" ], "evidence": [ "宝典区分两类离开并给出冷静期做法", "书总结大三迷茫期与毕业期两个高发时点", "书用连锁反应案例说明负向情绪蔓延的危害" ], "limits": [ "离开自由应被尊重，挽留不等于施压", "离职原因信息涉及隐私，不外传", "本卡不替代劳动合同或协议约定" ], "sourceBasis": [ "《穷学生宝典（第一版）》第二部分 · 关于成员主动离开" ], "tags": [ "成员离开", "挽留", "连锁反应", "人才储备" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:732a639453704d2f309b351e840ed11320e98dbd288f19a94362a44cf728e599", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-self-discipline", "title": "负责人的自我要求与权威", "domain": "负责人必修", "summary": "负责人以身作则遵守制度、保持职业形象，用专业与人格魅力而非职位建立权威，团队问题首先是负责人的问题。", "plainLanguage": "负责人是最容易破坏规则的人，也是唯一不能破坏规则的人。权威不是位置给的，是专业和言行攒出来的。", "keyPoints": [ "穿着得体、精神饱满，个人形象代表团队形象", "商务场合着装成熟专业，不刻意强调学生身份", "负责人带头遵守制度，否则制度形同虚设", "团队的任何问题都是负责人的问题，推卸责任的话不说", "权威由弱到强四层：职位、奖惩、专业水平、人格魅力", "再晚睡第二天也不能迟到打瞌睡" ], "useWhen": [ "新任负责人建立威信", "制度松散期的整顿", "对外商务形象准备" ], "workflow": [ "对照四层权威自评当前状态", "列出自己最容易破坏的规则并公开承诺遵守", "建立规律的作息与形象管理习惯", "遇到问题先内归因再向外协调", "用专业输出（技术、方案、演讲）积累公信力", "定期请成员反馈自己的言行问题" ], "evidence": [ "宝典分形象素质、遵守制度、建立权威公信力三节论述", "书给出权威由弱到强的四层来源", "书强调负责人要以德服人、严于律己" ], "limits": [ "权威不等于压制意见，仍需接纳批评", "形象要求应量力而行，不造成经济负担", "本卡为行为准则，不是处分依据" ], "sourceBasis": [ "《穷学生宝典（第一版）》第二部分 · 关于自我要求" ], "tags": [ "自我要求", "权威", "以身作则", "公信力" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:6f35b1858936c9352b9a36541a722e31d5cbe34f7c104826eaaa0051f1aa8a4a", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-work-time", "title": "工作时间与请假制度", "domain": "骨干运营", "summary": "固定上下班时间、打卡考勤、严格请假的非上课就上班制度，用统一节奏换来凝聚力与执行力。", "plainLanguage": "松散的出勤养不出能打仗的团队。把上班时间定死、考勤上打卡机，请假才会变成一件需要认真对待的事。", "keyPoints": [ "开学收齐课表，选课尽量集中在周一到周五", "周六日全天上班，每周放假半天到一天", "建议每天至少 9 小时分三个时段，树立非上课就上班观念", "引进打卡机记录考勤，周例会通报", "迟到一次罚款 100 元缴入创业基金", "寒暑假是集中开发与增收的关键期，建议暑假 5 天、寒假 7 天" ], "useWhen": [ "制定或整顿团队考勤制度", "安排学期与假期工作计划", "复盘出勤与执行力问题" ], "workflow": [ "学期初收集课表并排班", "全员讨论确定上下班时段", "引入打卡并公布考勤规则", "周例会通报考勤与迟到处理", "考前统一放假备考并设累计上限", "寒暑假前制定详细工作计划" ], "evidence": [ "宝典给出三段式作息与考勤、罚款入基金的具体规定", "书建议暑假放 5 天、寒假放 7 天（年前 2 天年后 5 天）", "书收录了固定上下班时间后团队战斗力明显改善的案例" ], "limits": [ "罚款规则需事先经全员同意并明确去向", "作息强度要保障健康与学业底线", "制度需随校历与考试周期弹性执行" ], "sourceBasis": [ "《穷学生宝典（第一版）》第三部分 · 关于请假 / 关于寒暑假" ], "tags": [ "考勤", "请假", "工作时间", "寒暑假" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:a1e7d8601d982cd34b476b03c0cce1690053d94632471bff577c4f2d01bec6ed", "readingPriority": "P1", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-no-salary", "title": "在校不领工资：长期主义与延迟满足", "domain": "骨干运营", "summary": "在校创业期间不领工资，把利润沉淀为团队生命线，用长期主义、坚定信念和延迟满足筛选真正的核心成员。", "plainLanguage": "在校不发工资不是抠门，是把每一分利润变成团队活下去的底气，顺便筛出真正相信这件事的人。", "keyPoints": [ "团队资金是生命线，积累越多抗风险能力越强", "大三迷茫期与毕业期尤其需要资金托底军心", "不发工资的三重逻辑：长期主义、坚定信念、延迟满足感", "零工资自然筛出愿意长期同行的核心成员", "毕业离校后再考虑发放补贴保障基本生活", "阳光灿烂的日子修屋顶，每天保持危机意识" ], "useWhen": [ "讨论团队分配与激励制度", "向新成员解释为什么不发钱", "复盘资金储备是否充足" ], "workflow": [ "把不领工资写入制度并在加入前讲清", "利润按既定比例留存团队账户", "定期公示资金积累进度与用途", "以蓝图与成长回馈代替物质激励", "离校前完成一轮资金目标核算", "毕业后按经营状况设计补贴方案" ], "evidence": [ "宝典明确提倡在校创业期间不领工资", "书从长期主义、坚定信念、延迟满足感三方面论证", "书提醒发过工资很难再停，物质激励要慎用善用" ], "limits": [ "劳动报酬涉及法律关系，注册公司后须依法处理", "不领工资仅适用于在校共创阶段", "不得以不发工资为由逃避既有承诺" ], "sourceBasis": [ "《穷学生宝典（第一版）》第三部分 · 关于在校期间领工资" ], "tags": [ "不发工资", "长期主义", "延迟满足", "资金储备" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:a7c1f59b8fd57760de99de3994a18acd861e6119c0eb7bd21a403b738eca5125", "readingPriority": "P1", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-culture-consensus", "title": "企业文化：共识比文档重要", "domain": "负责人必修", "summary": "使命愿景价值观的价值不在文字而在共识，用漫长的共同讨论与基本法共建，让制度深得人心。", "plainLanguage": "一家公司花 9 个月、每周三四个小时讨论二十多个字的使命愿景。文字不重要，讨论出来的共识才重要。", "keyPoints": [ "企业文化渗透在企业活动与统一风格里，不只是标语", "制度的关键是共识，讨论的过程就是达成共识的过程", "某届团队毕业后成立的公司花 9 个月讨论使命愿景价值观", "基本法由高管一字一句共建，规定各方案权利义务并在所有人之上", "深度参与底层建设的成员才会真正遵守规则" ], "useWhen": [ "启动团队使命愿景价值观讨论", "制定或修订团队基本制度", "文化传承与换届交接" ], "workflow": [ "排定讨论节奏（每周固定时段）", "逐词逐句讨论使命愿景价值观并投票", "把结论沉淀为成文文本", "以同样方式共建基本法条款", "新成员加入时讲透每条制度的含义", "定期回顾文本与实际行为的偏差" ], "evidence": [ "宝典记录了 9 个月讨论 20 多字与基本法讨论两年的案例", "书强调有没有文字不是重点，高度认可并形成共识才是关键", "书认为基本法深得人心源于全员深度参与" ], "limits": [ "讨论周期按团队节奏裁剪，避免议而不决", "基本法内容不得违反法律法规", "文本属于内部资料，公开前需去敏" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于建设企业文化" ], "tags": [ "企业文化", "共识", "基本法", "使命愿景" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:63c5d4cadf2608b60e9b8e1ae44336169ce2c4a9928e001565c77c66ba609ab9", "readingPriority": "P2", "relatedProjects": [ { "projectId": "teach-culture-consensus", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-team-first", "title": "团队利益高于个人利益", "domain": "负责人必修", "summary": "以特种部队的排序理解团队使命优先，力出一孔、利出一孔，早期不用绩效提成驱动联合创始团队。", "plainLanguage": "特种部队的排序是使命、队友、自己。创团队的版本是：团队利益、同伴利益、个人利益——长期看这三者本来就是一个东西。", "keyPoints": [ "团队使命大于队友的命大于自己的命，代表极致执行力", "力出一孔：全部力量集中一个点；利出一孔：收益只来源于团队", "成员不背团队以个人方式接单私活", "早期用共同梦想与共识规则驱动，不用绩效提成", "绩效容易让成员计较短期，不适合联合创始团队", "负责人先放弃个人利益，才配谈团队利益" ], "useWhen": [ "处理个人利益与团队安排的冲突", "设计早期激励方式", "整顿私单与精力分散问题" ], "workflow": [ "把团队优先写入制度并在加入时讲清", "明确禁止私单与副业冲突的边界", "早期激励以目标达成与成长反馈为主", "负责人以身作则示范利出一孔", "出现冲突时按长期价值原则裁决", "规模扩大后再引入正式绩效体系" ], "evidence": [ "宝典用《特种部队》的排序说明极致团队状态", "书明确力出一孔、利出一孔的含义与负责人身先士卒的要求", "书分析绩效提成对早期团队的分裂风险" ], "limits": [ "团队优先不等于无条件牺牲，注意身心健康", "注册公司后雇员必须依法计酬", "禁止私单的范围应在加入前书面确认" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于团队利益和个人利益" ], "tags": [ "团队利益", "力出一孔", "利出一孔", "绩效" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:bd007cf1dd79611573af43654c53ca2b1d0187e0608c492bda278aae1510893f", "readingPriority": "P2", "relatedProjects": [ { "projectId": "teach-culture-consensus", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-decision-making", "title": "团队决策：早期集权后期民主", "domain": "负责人必修", "summary": "早期偏集权保执行效率，后期偏民主培养干部；用口袋方案、对事不对人和基本法把决策质量与制衡固定下来。", "plainLanguage": "听谁的？听对的。决策与人切割，观点与事实分离；早期快刀斩乱麻，后期开放讨论养干部。", "keyPoints": [ "集权执行快、一种声音，但成败系于负责人判断", "民主能培养干部、集合智慧，但决策慢且执行易打折", "建议在校早期偏集权，争分夺秒统一思想", "开会前负责人先备好口袋方案，有更好的就用更好的", "不听谁的，听谁是对的：把观点和人切割开", "后期用制衡与基本法固定基本原则，防止独断" ], "useWhen": [ "设计团队决策机制", "处理重大分歧", "负责人自评决策质量" ], "workflow": [ "重大事项会前形成至少一个完整方案", "会议先征集意见再出示口袋方案", "按观点质量而非身份裁定", "宣布决策、明确执行人与时限", "记录决策依据便于复盘", "定期让核心成员参与决策以培养判断力" ], "evidence": [ "宝典对比集权与民主的优劣并建议早期集权", "书强调十个人有十个观点但不会有十个事实", "书要求用基本法约束基本原则并给负责人设置制衡" ], "limits": [ "集权决策的后果由决策者承担，需留复盘记录", "涉及成员重大利益的决策应充分征求意见", "民主与集权按阶段切换，不教条" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于团队决策" ], "tags": [ "决策", "集权", "民主", "制衡" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:bfe773ea7375cf17e7f63001041685e2e595c088901fd911fdcd3f0b986075aa", "readingPriority": "P2", "relatedProjects": [ { "projectId": "prof-campus-ride", "basis": "V13 项目档案实体建立（prof-campus-ride），兑现 P0 pending 线索（知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-split-prevention", "title": "团队分裂的防范与底线", "domain": "负责人必修", "summary": "分裂多起于双狼局面与负责人失衡，用日常团结、提前约定资金归属和保住传承底线来降低伤害。", "plainLanguage": "分裂的种子在日常就埋下了。负责人要常常自省、不偏不倚，并且提前约定：无论谁走，资金和传承都留在原团队。", "keyPoints": [ "分裂通常源于头狼与挑战者实力差距不够悬殊的双狼局面", "负责人先反思自己是否做得不够好，不搞亲疏远近", "规定原团队拥有所有资金，挑战者不能带走任何资金", "若两人都适合做负责人，早分开各自发展好过晚期相争", "任何一届分裂都不能影响网维的传承", "日常不公开表达与某个成员关系最好" ], "useWhen": [ "察觉团队内部张力上升", "处理负责人之争的苗头", "修订资金与退出条款" ], "workflow": [ "日常用客观评价代替亲疏表达", "出现挑战苗头时先自省管理短板", "二选一：用实力让对方佩服或和平分开", "按约定确认资金与资产归属", "把影响控制到最小并稳定军心", "确保传承计划不受人事变动中断" ], "evidence": [ "宝典分析双狼局面与两种应对：容下或淘汰", "书规定原团队拥有所有资金以保护传承", "书强调分裂断传承是最需要避免的结果" ], "limits": [ "资产归属以书面协议为准", "分裂处置涉及人身关系，注意方式方法", "本卡不替代法律意见" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于团队分裂" ], "tags": [ "团队分裂", "双狼", "资金归属", "传承" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:cbb7c523196412aed760a7a20d4aba9e877255091d47f62ecfd8819d96c8ba4c", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-influence", "title": "扩大影响力：B 端 demo 与 C 端流量", "domain": "负责人必修", "summary": "备好长短两版团队介绍，用会友、合作冠名等打法做 B 端影响力，按平台/内容/变现三板块理解 C 端流量机会。", "plainLanguage": "电梯 3 分钟讲不清团队是谁，就别指望别人记住你。B 端靠 demo 和合作，C 端靠流量，流量本身就是商业机会。", "keyPoints": [ "团队介绍准备 3 分钟短版与 30 分钟长版并持续迭代", "B 端方法：会友、节日拜访、机构合作、系统冠名、校内宣传", "C 端先研究推广渠道与用户心理，再谈产品", "互联网生意三板块：做平台、做内容、流量变现（含中间商）", "流量红利动态变化，找项目先找优质流量渠道", "上线的系统要留下团队标识与联系方式" ], "useWhen": [ "准备路演、宣讲或拜访材料", "规划品牌与推广预算", "评估一个项目要不要做推广" ], "workflow": [ "写并背熟 3 分钟团队 demo", "制作长版材料用于会友与合作方", "梳理可合作的校内外机构清单", "在交付系统上落实团队冠名与入口", "跟踪主流平台的流量成本与玩法", "定期复盘影响力动作的转化" ], "evidence": [ "宝典分 B 端与 C 端两节给出具体打法", "书强调项目推广就是一切并给出流量三板块框架", "书提醒流量即商业机会，找项目先找流量" ], "limits": [ "平台玩法时效性强，需按当期重新调研", "宣传不得夸大团队业绩", "投放涉及付费决策，先小规模验证" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于扩大团队影响力" ], "tags": [ "影响力", "demo", "流量", "B端", "C端" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:ab53d6a9c5c112c4a3193d4ca90c3ad1450195c276342a130462020761150510", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-execution", "title": "执行力三步：定目标、追过程、拿结果", "domain": "负责人必修", "summary": "用 SMART 定高目标、主动跟进给资源、验收并奖惩，把一流执行力变成团队的可复制流程。", "plainLanguage": "三流的想法加一流的执行力，胜过一流的想法加三流的执行力。执行力的差距全在三步：定目标、追过程、拿结果。", "keyPoints": [ "目标按 SMART 原则制定，设高目标带来高标准", "长周期任务要拆解出阶段性胜利，避免懈怠", "分配后主动跟进监督并给予资源支持", "下属要主动汇报，双向沟通才高效", "完成后按制度验收并落实奖惩", "把合适的人放在合适的任务上" ], "useWhen": [ "项目总是延期时的流程整顿", "任务分配与验收标准设计", "复盘被抢跑或烂尾的项目" ], "workflow": [ "用 SMART 把目标写成可验收的句子", "拆解到周并明确每步负责人", "建立固定节奏的进度检查点", "阻塞当天升级、当天协调资源", "按验收标准评价并兑现奖惩", "把延误原因写回计划模板" ], "evidence": [ "宝典给出定目标、追过程、拿结果的完整方法与案例", "书收录了校园约车因执行力不足被抢跑的去敏案例", "书强调所有管理维度最终都为执行力服务" ], "limits": [ "高目标要配套资源，不能只施压不给支持", "奖惩规则需事先公开", "追过程不等于微观管理，抓关键节点" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于提高团队执行力" ], "tags": [ "执行力", "SMART", "追过程", "拿结果" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:30479618ef715340f6de175b22359dcc864359ddd5874b101b5d4cdbaffbd37c", "readingPriority": "P2", "relatedProjects": [ { "projectId": "teach-blueprint-progress", "basis": "教学映射 mapsTo（V5-V6 建立的知识层证据）", "evidenceLevel": "distilled" } ], "projectLinkStatus": "linked", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-honor", "title": "团队荣誉感的营造", "domain": "负责人必修", "summary": "把荣誉分给大家：用仪式、公示、表扬和活动四个场景持续积累团队自豪感，让成员发自内心维护集体声誉。", "plainLanguage": "荣誉感不是喊出来的，是设计出来的：入队有仪式、加入有公示、成果有表扬、年年有答谢。", "keyPoints": [ "负责人不抢功，把荣誉归给成员是基本姿态", "成立仪式、宣誓与创业基金是荣誉感的起点", "新成员加入要公示并介绍，这是团队的责任", "项目交付、获奖、客户认可都要公开表扬", "年度答谢酒会等场合收获外部肯定", "荣誉感驱动凝聚力、归属感与自发维护" ], "useWhen": [ "新成员入队与团队 milestones 时刻", "士气低落期的团队建设", "对外展示与品牌积累" ], "workflow": [ "建立入队仪式与公示的固定流程", "为每个成果设置公开表扬的场合", "年终举办答谢活动邀请各方", "沉淀荣誉墙、徽章等可视化载体", "对外宣传时突出团队而非个人", "把外部好评回流给相关成员" ], "evidence": [ "宝典给出营造荣誉感的四个具体场景", "书引用任正非把荣誉归功于团队的态度作对照", "书认为荣誉感来自业务成果与外部认可的日积月累" ], "limits": [ "表扬要真实，杜绝包装式荣誉", "公示信息需征得成员同意", "活动开支遵守团队预算纪律" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于团队荣誉感" ], "tags": [ "荣誉感", "仪式", "公示", "表扬" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:b24c636faf42fa2fecf6db8643cd266583f94ac45a723506c0023a95dbfae935", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-junior-year", "title": "大三迷茫期：负责人的定海神针", "domain": "骨干运营", "summary": "约三分之一成员会被大三迷茫期击退。提前规划路径、持续积累资金、多带团队见师兄，是穿越动荡的三个抓手。", "plainLanguage": "大三那年，身边人都在拿 offer、考研、出国，动摇是必然的。CEO 唯一要做的是提前把路铺好，让大家忙得没空迷茫。", "keyPoints": [ "迷茫期是大三人生抉择的必然产物，约 1/3 成员在此离开", "CEO 没有规划未来，成员就会自己规划", "提前想清商业模式、资金缺口与阶段方案", "大一大二就要积累资金，避免大三被动", "多带团队走出学校，见师兄看成功案例", "用足够多的项目与稳定收入让大家忙碌且坚定" ], "useWhen": [ "大三学年的团队预案", "成员出现动摇迹象时", "资金储备与业务节奏规划" ], "workflow": [ "开学即公布学年目标与离校路线图", "为每人安排清晰的任务与成长承诺", "保证每月稳定的项目收入进账", "组织 1-2 次拜访毕业师兄团队", "对动摇成员提前一对一沟通", "期末复盘留任情况并调整计划" ], "evidence": [ "宝典给出约三分之一成员被大三迷茫期击退的数据", "书要求 CEO 提前规划并承担方向责任", "书建议多和师兄师姐接触用成功案例稳军心" ], "limits": [ "迷茫是个体选择的一部分，尊重不同道路", "收入承诺不夸大，按真实业务预测", "规划不能替代成员自己的决定" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于迷茫期" ], "tags": [ "迷茫期", "大三", "留任", "规划" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:8198a04310f330a0dd28db4c8e23a1260cecac3404fb212d936087a2a27fafe4", "readingPriority": "P1", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-leave-school", "title": "离校创业：早出来，早现实", "domain": "负责人必修", "summary": "建议大三寒假或暑假把团队搬出学校，用成本压力倒逼成长；离校前完成心理与资金的双重准备。", "plainLanguage": "在学校里可接可不接的单，出了校门就是必须拿下。早半年面对真实成本，团队就早半年完成学生到创业者的转变。", "keyPoints": [ "多位毕业负责人共识：越早离开学校越好", "建议大三寒假或暑假整体离校", "离校前定好城市、办公室与每月固定开销", "资金目标按 50 万到 100 万积累去冲", "做好租不起写字楼、住居民房的心理准备", "毕业后开始考虑发工资与补贴" ], "useWhen": [ "制定离校创业时间表", "估算离校后的成本与订单压力", "评估团队是否具备离校条件" ], "workflow": [ "提前确定离校时间点并全员对齐", "踩点目标城市的办公室与住所成本", "核算无订单情况下的资金存活月数", "打包交接校内资源给下一届", "离校后按周复盘订单与现金流", "节衣缩食但保证基本健康底线" ], "evidence": [ "宝典多处强调尽早离校创业并给出资金准备建议", "书收录多个去敏的节衣缩食案例（合租、蹲路边吃饭等）", "书把离校称为宣告独立的转折点" ], "limits": [ "离校时点需兼顾学业与家庭意见", "成本数据为历史经验，需按当地现价核算", "未达资金底线时优先推迟而非硬撑" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于离校创业" ], "tags": [ "离校创业", "成本", "资金准备", "转折点" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:c132de3dc6d0b1612cb5254f44dfee0cd1e7e867a494ad741f53f67984b9e1ba", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-tech-to-biz", "title": "技术转业务：放下代码去做市场", "domain": "骨干运营", "summary": "业务与技术同样决定生死，成员按公司需要渐进转业务，关键是把表达练好、贴近真实市场需求。", "plainLanguage": "埋头写代码最容易做出假象需求。技术转业务不是转行，是把技术能力翻译成客户听得懂的价值。", "keyPoints": [ "早期业务一定由负责人先拿下，负责人必须懂业务", "没有固定转岗时间，公司需要时就是时候", "联合创始人后期转管理或业务是必然", "只钻技术容易与真实需求之间产生巨大鸿沟", "渐进式培养：发现业务潜质就往该方向带", "转业务的关键是把表达练好并调整心态" ], "useWhen": [ "安排成员的岗位发展方向", "团队业务扩张期的人手布局", "技术型成员的转型辅导" ], "workflow": [ "评估当前业务缺口与技术冗余", "选定转型人选并明确过渡期", "以跟随拜访、共同提案方式带教", "把技术背景转化为方案讲解优势", "复盘每次商务洽谈的话术与结果", "逐步独立负责客户与交付" ], "evidence": [ "宝典指出业务决定公司命脉并给出渐进培养建议", "书强调技术牛与客户需求之间有巨大鸿沟", "书建议邀请业务型负责人分享经验帮助转型" ], "limits": [ "转型期间技术交付需有人接续", "尊重成员意愿，避免强转引发流失", "商务承诺不得超出团队交付能力" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于成员从技术转业务" ], "tags": [ "技术转业务", "转型", "客户沟通", "培养" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:9a805c2182f40d7a7586bff6025b9107e868a15fb0e3693466eb4a5fa69ab051", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-competition", "title": "创业比赛：慎参赛，护机密", "domain": "骨干运营", "summary": "比赛耗时间且可能泄露商业模式：低年级先攒实力不轻易参赛，高年级真创业的数据天然能打，BP 只对投资人在私下场合展示。", "plainLanguage": "靠比赛挣 10 万和靠市场挣 10 万是两回事。真创业的团队拿奖不难，难的是守住自己的商业模式。", "keyPoints": [ "打比赛与真创业是两种打法，比赛分散精力拖累项目", "低年级不轻易参赛，没有项目就去找项目、加强内训", "高年级可参赛且应拿好名次：真实数据就是竞争力", "商业计划书就是商业机密，台下都是头狼", "参赛可保办公室、给学校交代，是现实收益", "靠比赛奖金养团队不可持续，市场才能证明实力" ], "useWhen": [ "收到参赛邀请时做取舍", "权衡比赛与项目交付冲突", "准备路演材料的保密边界" ], "workflow": [ "评估参赛对业务与办公室的影响", "只展示可公开的部分商业模式", "用真实项目数据替代包装内容", "控制参赛投入的时间上限", "赛后把有用反馈写回项目计划", "保护核心数据与客户信息不外泄" ], "evidence": [ "宝典用整章分析参赛的收益、风险与时机", "书强调好项目一旦暴露就有一百个人做", "书认为比赛融资并不常见，资金主要靠自挣" ], "limits": [ "各校对比赛的扶持政策不同，需按实际权衡", "路演材料公开前需团队评审", "不夸大成绩、不虚报数据" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于创业比赛" ], "tags": [ "创业比赛", "商业机密", "取舍", "路演" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:5c7d328a3b6f858f0c9f26cb97670d562206c9a1a5536e2ec319ce22cb35cde7", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-teacher-boundary", "title": "指导老师：借力而不依赖", "domain": "负责人必修", "summary": "指导老师是外部支持而非决策者：借力争取资源、保持独立决策，老师参股只在两种逻辑下可考虑。", "plainLanguage": "老师愿意帮是运气，但团队的方向必须自己拿。老师跳过负责人直接给成员派活，就说明边界已经破了。", "keyPoints": [ "找不找指导老师都可以，要找就选有威望的", "老师可帮助争取政策、场地与校内支持", "老师不能干预团队决策、不能深度参与运营", "老师跳过负责人直接布置任务是有问题的信号", "老师入股仅两种逻辑：全职加入创业，或作为不影响决策的天使投资人", "不要过于依赖老师，团队要独立发展" ], "useWhen": [ "确定是否聘任指导老师", "划清与老师的协作边界", "处理老师资源入股的提议" ], "workflow": [ "按威望与理念认同度筛选老师人选", "以会友方式让老师了解团队制度与初心", "明确老师支持的范围与方式", "发现越界介入时由负责人及时沟通", "对外表述保持团队独立身份", "换届后完成师生关系的重新对接" ], "evidence": [ "宝典专章讨论指导老师的选择、作用与边界", "书明确老师不能干预决策、不能跳过负责人派活", "书给出老师参股的两个可考虑逻辑" ], "limits": [ "与老师的关系需尊重校规校纪", "资源入股涉及公司治理，需法律意见", "本卡不针对任何具体教师个人" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于指导老师" ], "tags": [ "指导老师", "边界", "独立性", "校内资源" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:bdc82c6d6bce009e1ddacc14e38323d3acddcbd48b10e359ba97d119963c2ba6", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" }, { "id": "aaaw-book-company-registration", "title": "注册公司：理解这个组织形式", "domain": "负责人必修", "summary": "注册本身建议交代办，更重要的是理解公司这一组织形式的价值：它把梦想、制度与责任装进一个可持续的容器。", "plainLanguage": "注册公司不难，难的是明白公司是什么：三百年来最厉害的组织形式，也是装下你们梦想的那条船。", "keyPoints": [ "注册流程建议找代办，省时省力", "公司是现代经济最重要的组织形式，承载就业与创新", "公司制度与市场经济发展是同一件事", "面向市场创新的组织才是知识变力量的关键", "注册前先完成股权、退出机制与基本法的讨论", "WTEAM 的本质：学做 CEO、建执行团队、等市场机会、拿结果" ], "useWhen": [ "筹备注册公司的时间表", "理解公司治理与团队制度的关系", "向成员解释注册的意义" ], "workflow": [ "确认股权结构与协议文本（见股权卡）", "选择代办并核对注册地与行业类目", "准备章程、账户与财务制度", "完成注册并归档证照材料", "把团队制度映射为公司制度", "按期完成税务与年报义务" ], "evidence": [ "宝典建议找代办注册并引《公司的力量》论述组织价值", "书总结 WTEAM 的本质是学 CEO、建团队、等机会、拿结果", "书提醒注册前把股权与退出机制谈清楚" ], "limits": [ "具体注册与税务要求以当地法规为准", "本卡不构成法律或财税意见", "证照与账户信息属敏感资料，不得公开" ], "sourceBasis": [ "《穷学生宝典（第一版）》第四部分 · 关于注册公司" ], "tags": [ "注册公司", "代办", "组织形式", "公司治理" ], "evidenceLevel": "document", "visibility": "public", "contentStatus": "published", "lastReviewedAt": "2026-10-30", "publicVersion": "sha256:136d983b2b1d3ea3e6b721d3430d53f2ace4ee56e24f4ece8e833d6d12ec723b", "readingPriority": "P2", "relatedProjects": [], "projectLinkStatus": "none", "projectLinkNote": "暂无适用项目案例（制度/理念类知识点，不以关联数量为指标）", "contentType": "concept", "ownerRole": "待指定", "nextReviewAt": "2027-02-02" } ] }