Skip to main content
Employee groups let multiple Wakers collaborate. You bundle several Wakers into a group and designate one Leader Waker to understand the goal, break down the task, coordinate members, and consolidate results — while the member Wakers each execute their part. Everything happens in a Group Chat, where you can ask questions, follow up, or steer the direction at any time. Before you start, make sure you’re signed in to QoderWake and have at least a few Wakers available to form a group.

​
Create an employee group

  1. Open the chat page and click New Group.
  2. Name the group. Use a task-related name that’s easy to recognize, e.g. “Competitor feature analysis” or “Multi-task board design review.”
  3. Pick the Leader Waker — the task owner who understands the goal, breaks down the steps, coordinates members, and consolidates results.
  4. Add member Wakers — mix and match by task needs, e.g. a Product Waker, an Engineering Waker, a QA Waker.
  5. Once created, you enter the group and can start collaborating.

​
Kick off a task

Type your question or goal straight into the Group Chat. Simple questions can go in as-is; for complex tasks, add context, goals, and constraints so the Leader Waker can organize the work better. For example:
  • “We want to design a multi-task board for the console that shows the status, member assignments, and milestone results of multiple employee-group tasks. Break it down from product design to technical solution, and give me an actionable development plan.”
  • “Analyze a feature a competitor recently shipped, judge its impact on our product, and output a feature overview, key changes, opportunity assessment, and recommended actions.”

​
How the Leader Waker responds

After you send a task, the Leader Waker first reads your intent, then decides how to proceed: lightweight questions get answered directly or routed to a member for detail; complex tasks are broken into phases, with member assignments and a next-step plan. If the direction isn’t what you expected, correct it right in the Group Chat:
  • “Focus on engineering delivery — no need to expand the go-to-market section.”
  • “Produce a product flow first, then move into the technical solution.”

​
Collaborating with member Wakers

The core value of an employee group is different Wakers dividing the work around one shared context. You can ask a specific member to fill in details or do a review, or have the Leader Waker consolidate the current conclusions:
  • “Engineering Waker, walk through the main technical risks of this approach.”
  • “QA Waker, add edge cases and regression scenarios.”
  • “Leader Waker, consolidate everyone’s conclusions so far.”

​
Step in and adjust anytime

You can interrupt, follow up, or change the goal at any point. Common moves:
  • “Where does the task stand now? Summarize it as a list.”
  • “Pause the development plan — prioritize the user journey and page states first.”
  • “Pull the current conclusions into a version I can send for engineering review.”
Employee groups fit tasks that need division of labor, sustained progress, milestone summaries, and final delivery — for example:
  • Solution delivery — cross-role product discussion and implementation.
  • Issue diagnosis — end-to-end collaboration from triaging an issue to submitting a PR.
  • Software development — complex tasks that need product, engineering, and QA working together.