CM108G 1151 Management | Weekly Assignment Draft

Status: English learner-facing draft v0.1 | 2026-09-06 | prepared for Microsoft Teams

Course source: CM108G 1151 course page

This English version is the source for learner-facing Teams assignments. It keeps the workload small, makes each week's expected output concrete, and avoids asking students to rewrite earlier work in full.

1. Semester schedule

Weeks 4 and 8 are self-study weeks because there is no class meeting. Week 16 remains the final exam week. Weeks 17 and 18 still have class and therefore still have assignments.

2. Rules included in every Teams assignment

Files and AI collaboration logs

1. Submit both the assignment and a log file. Suggested names are WXX_studentID_assignment.md and WXX_studentID_log.md; a group may use its group name instead of a student ID.
2. The assignment and the log must be Markdown (.md) or plain text (.txt). Word, PDF, HTML, spreadsheet, image-only, screenshot-only, and other formats are not accepted.
3. If you use ChatGPT, Gemini, NotebookLM, or another AI tool, include evidence in the log: the tool, date, purpose, main prompt, useful output, fact-checking, and what you changed or rejected.
4. Export AI conversations with ChatGPT Exporter, Gemini Exporter, or a comparable exporter. Submit the exported evidence as Markdown or plain text. Do not submit the export as PDF, HTML, or screenshots.
5. If you did not use AI, submit a log that says so and records your sources, reasoning, and final checks. An empty log is not acceptable.
6. A log is more than a pasted AI transcript. It should show your own starting point, the role of AI if any, how you checked the information, and why you kept or rejected suggestions.
7. The AI rule for the week will be stated in the assignment. The teacher's latest weekly announcement takes priority over this general rule.

Writing format

• Use headings, short paragraphs, and Markdown tables where they make the work easier to read. A .txt file should use clear headings and indentation.
• Explain the reason behind each important judgment. Add working links and basic source details for outside material.
• Image-only work, screenshot-only tables, and unedited AI output are not accepted.
• Keep the work focused. A short, well-supported answer is better than a long report that repeats the case.
• If the evidence is not enough, write "evidence is not yet available" and list what needs to be checked. Do not invent facts, figures, people, or company information.

Format gate and resubmission

The file rules are a submission gate. If the assignment body, log, required exporter evidence, accepted file format, or group member list is missing, the submission does not count and will not enter formal grading. You must resubmit a complete version before it can be graded. A high content score cannot replace a missing or invalid file.

Late policy

• The normal deadline is 11:30 PM on the evening before class.
• A submission after the deadline receives a 15% deduction after the original score is calculated.
• A submission first made after the semester ends receives a 30% deduction.
• Resubmitting an invalid-format file does not remove the late penalty. The relevant time is the first submission that meets all format requirements.
• The 30% end-of-semester deduction replaces, rather than stacks on top of, the normal 15% late deduction.

Individual and group work

• For individual work, each student submits their own assignment and log and identifies themselves by student ID and official Chinese name. No group name is needed.
• For group work, one representative submits for the group. The assignment must list every member's student ID and official Chinese name. English nicknames such as Cindy or Jason are not sufficient.
• The representative must check that the assignment, complete member list, shared log, and all relevant AI records are included. If members used AI separately, the shared log must identify each person's use or non-use and point to each person's exporter file.
• Weeks 1 and 2 are individual. Group work begins in Week 3 unless a weekly announcement says otherwise.

Changes to an assignment

The assignment, deadline, file rules, or rubric may change when the course schedule, case evidence, Teams interface, or assessment needs change. When a change is made, the teacher will repost the assignment notice. Always follow the most recent reposted version.

3. Weekly assignments

Week 1 | Getting started: build useful Teams Rubrics

• Format: Individual. The class has not formed groups yet.
• AI mode: Follow the teacher's weekly announcement. Do not assume that AI is allowed from this draft.
• Time: About 30–40 minutes.
• Task: Use rubric-framework-v0.1.en.md as a starting point and draft five Teams Rubric criteria. For each criterion, include its purpose, observable evidence, what is missing when the work falls short, and a suggested score or level structure.
• What good work looks like: A student should be able to use your Rubric to prepare the assignment, and a teacher should be able to use it to grade observable evidence. Avoid vague labels such as "good," "complete," or "deep" without explaining what they mean.
• Submit: One Markdown or TXT file with five criteria and one log. For each criterion, note which part of rubric-framework-v0.1.en.md you used and add one sentence explaining how a student would prepare for the assignment under that criterion. This week asks you to design Rubric criteria; you do not need to create or publish a formal assignment in the course Teams site.
• Rubric focus: Clear criteria, observable level differences, sensible scoring, and a complete Markdown/TXT submission with a usable log.

Week 2 | The manager's role: from creator to owner

• Format: Individual.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 25–30 minutes.
• Task: Create a one-page role map for at least four roles Judy may hold at the same time. For each role, explain the goal, pressure, required capability, and work that could be delegated or handled by an outside partner.
• Focus: Do not simply list job titles. Explain where the roles pull against one another and which conflict you would address first.
• Submit: A Markdown/TXT role map and log. If you use a table, include role, goal, pressure, capability, possible delegation, and your judgment.

Week 3 | Decision-making with incomplete information

• Format: Group work. One representative submits; the main file lists all members' student IDs and official Chinese names.
• AI mode: Follow the teacher's weekly announcement.
• Time: 10–15 minutes for each first judgment, plus about 20 minutes for group integration.
• Task: Each member first records a core question and provisional judgment. The group then prepares a one-page decision memo with the core problem, at least two options, three decision criteria, evidence quality, and a provisional choice. Add a short note on roles, the shared team database, and one team-health check.
• Focus: Name one uncertainty and explain what new evidence could change the decision.
• Submit: Decision memo, each member's first judgment, team roles/health-check note, and one shared log.

Week 4 | Self-study and reflection during the Teacher's Day holiday

• Format: Individual self-study and reflection.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 20–30 minutes.
• Task: Complete the reflection activity assigned by the teacher. At minimum, connect one management idea to one case or reading observation, identify one opportunity and one constraint in a Taiwan, Korea, or wider Asian Chinese-speaking market, and state one evidence gap or possible management action.
• Submit: A Markdown/TXT reflection and individual log. This is not a group submission.

Week 5 | Goals and planning: what should the company become?

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 30 minutes.
• Task: Prepare a one-page positioning and goal-setting document. State the position you choose, the position you deliberately reject, why you made that choice, and two or three goals that can be checked in the next stage.
• Focus: A goal should show a time frame, target, or observable result. "Grow," "become famous," and "increase revenue" are not enough on their own.
• Submit: Positioning and goals, member contributions, and a shared log.

Week 6 | Strategy and diversification: what belongs together?

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 30–35 minutes.
• Task: Compare at least three business lines or growth options. For each, state expected value, required capabilities, major cost or risk, fit with the company position, and the next short-term step. Choose what to keep, pause, outsource, or expand.
• Submit: Comparison table, a strategy position of no more than 200 words, member list, and shared log.

Week 7 | Core capabilities: what does Judy really have?

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 30 minutes.
• Task: List five to seven capabilities the case team may have. Classify each as something to build internally, obtain through a partner, or not invest in yet. Give a reason and observable evidence for every classification.
• Focus: Popularity, money, or a one-time opportunity is not automatically a core capability. Explain what can be reused, differentiated, or carried into the next stage.

Week 8 | Self-study and reflection during the make-up holiday

• Format: Individual self-study and reflection.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 20–30 minutes.
• Task: Complete the teacher's reflection activity on organization and people management. Address at least two of recruitment, training, scheduling/work allocation, evaluation, compensation, or grievance handling. State one important learning, one judgment you would revise, and one next step to check or carry out.
• Submit: A Markdown/TXT reflection and individual log. Do not submit a group summary or group name.

Week 9 | Midterm project progress: how would you run the company now?

• Format: Group milestone; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 60–75 minutes. Do not paste the first eight weeks in full.
• Task: Prepare a progress pack with five short parts: a management judgment, a business portfolio map, an initial operating plan, evidence/assumptions that still need checking, and a next-step plan.
• Length: Aim for no more than 1,200 words. Keep only the excerpts needed to support the current judgment.
• Submit: Progress pack, full member list, contribution note, and a shared log.

Week 10 | Teams and communication: the company cannot run on a chat group alone

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 30 minutes.
• Task: Draw or describe a communication system covering meetings, documents, decisions, reporting, exceptions, and information visibility. For each type of information, state who owns it, when it is updated, where it is stored, who can decide, and how delays are escalated.
• Submit: A Markdown/TXT system map or table, member list, and shared log. A picture without an accessible text explanation is not enough.

Week 11 | Operations and content quality: from filming to reliable delivery

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 35–40 minutes.
• Task: Design a short operating SOP with at least six key steps from starting the work to delivery. Mark the owner, quality check, backup plan, and acceptance condition for each step.
• Focus: An SOP should make work repeatable and transferable. Prioritize the steps most likely to fail.

Week 12 | Marketing and customers: different audiences have different needs

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 30 minutes.
• Task: Identify at least three customer or partner groups. For each, state the problem, reason to buy or collaborate, success measure, and main risk. End with the one assumption you would test first.
• Focus: Do not treat "all viewers" as one customer group. Explain why each group would give time, money, or cooperation.

Week 13 | Financial management: traffic is not the same as a business

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 35–45 minutes.
• Task: Compare conservative, balanced, and fast-growth scenarios. For each, list key revenue sources, major costs or resource needs, assumptions, cash pressure, and a possible stop-loss point. A full accounting statement is not required.
• Focus: If reliable numbers are not available, label estimates as assumptions or write "evidence is not yet available." Do not present guesses as facts.

Week 14 | Motivation and leadership: from older sister to manager

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 30 minutes.
• Task: Design a short motivation system covering at least four of income, learning, exposure, participation, and role growth. Explain how it avoids rewarding short-term traffic alone.
• Focus: Address different needs and give people a fair way to raise and review a concern.

Week 15 | Ethics, risk, and change: trust can become a liability

• Format: Group work; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 30 minutes.
• Task: Build a table of at least five ethical or operating risks. Include the risk, trigger, affected parties, preventive action, response after the event, and any needed public explanation. Prioritize two risks.
• Focus: Consider trust, member rights, customers, partners, and reputation as well as financial loss.

Week 16 | Final exam week

• The final exam remains on 2026-12-21. There is no additional weekly assignment.
• The exam follows its own announcement and rules. The weekly assignment body/log, exporter, Markdown/TXT, rubric, and late policy do not apply unless the exam announcement says otherwise.

Week 17 | Final case analysis and recommendation

• Format: Group milestone; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 60–90 minutes. Reuse earlier tools; do not rewrite every earlier assignment.
• Task: Choose one growth path and present your team's version of the Judy company. Integrate the matching business model, management system, dashboard priorities, and next-quarter action plan. Link each major recommendation to evidence, an assumption, or an open question.
• Length: Aim for no more than 1,500 words. This is a case analysis, not a new individual reflection.

Week 18 | Company-building blueprint and course close

• Format: Group final blueprint; one representative submits with the full member list.
• AI mode: Follow the teacher's weekly announcement.
• Time: About 45–60 minutes.
• Task: Revise the Week 17 recommendation using feedback. The final blueprint should show the decision, action order, management system, measures, main risks, and information still needed.
• Length: Aim for no more than 1,800 words. Focus on integration instead of copying every earlier assignment. There is no new individual reflection this week; reflection work is scheduled in Weeks 4 and 8.