| Course | DIV 5003 Belonging and Inclusion in the Workplace |
|---|---|
| Module | Module 3 |
| Paper type | Inclusive collaboration practices design |
| Length | 1,210 words, about 4 pages plus title and reference pages |
| Format | APA 7 student paper |
| School | American College of Education |
| Program | M.S. in Organizational Leadership |
| Updated | October 2026 |
Free sample paper for DIV 5003 Module 3
Juniors Speak First and the Chat Gets Read: Designing Inclusive Design Reviews and Project Practices
Student Name
American College of Education
DIV5003: Belonging and Inclusion in the Workplace
Module 3 Assignment
Instructor Name
September 18, 2028
Introduction
Modules 1 and 2 showed that our design group accepts its members but does not draw fully on their views. Senior engineers hold most speaking time in design reviews, remote comments go unread and ideas that later improved designs surfaced by chance. This paper designs collaboration practices to change that. It reviews research on why groups miss information, sets out practices for design reviews and for projects, explains how each answers a problem found earlier and plans a pilot with measures.
Why Groups Miss Information
Stasser and Titus (1985), in experiments on group decision making, found that discussion gravitates toward facts everyone already knows, while a fact known to a single member often never surfaces, even when it would point the group to a better choice. Mesmer-Magnus and DeChurch (2009), in a meta-analysis, confirmed that information sharing predicts team performance and that sharing unique information, which only some members hold, matters especially. Nembhard and Edmondson (2006) showed that when leaders openly ask for and thank people for their contributions, psychological safety rises, particularly among lower-status members. The practices below are designed to surface unshared information and to make invitation routine rather than accidental.
Practice One: Pre-Read and Written Comments
Design review materials will be posted to the shared drawing viewer at least two working days before each review, and every member of the group can add written comments directly on the drawings during that window. Written comments give engineers who are less comfortable speaking up, remote engineers and those working in a second language a way to contribute before the meeting, at their own pace. The project lead will summarize the written comments at the start of the review, so the discussion begins with everyone's input rather than only with what senior engineers say in the room. This answers the crash map case, where an idea in an unread chat waited two weeks.
Practice Two: Juniors Speak First
In the review itself, comments on each design element will be taken in a set order, starting with engineers with the least experience and ending with the senior engineers who sign the drawings. When senior engineers speak first, others tend to adjust their views toward the senior opinion or stay silent. Reversing the order lets junior engineers state their observations before they know what the senior view is. The project lead will explain that this is a standard practice, not a test, and anyone may pass. The curb ramp case, where a junior engineer's concern was initially dismissed, shows why junior views need to be heard before a direction is set.
Practice Three: A Remote Facilitator
For every review with remote participants, one in-person attendee, rotating among the group, will serve as remote facilitator. That person monitors the chat, raises remote comments aloud at the next natural pause and confirms that remote participants can see the drawings being discussed. Drawings will be shared on screen through the viewer rather than only on the conference room display. These steps address the finding that remote engineers spoke for about 6 percent of review time and that their comments often arrived after the discussion had moved on. The facilitator role also builds a habit of noticing who has not yet spoken, which in-person attendees rarely track on their own.
Practice Four: An Alternatives Lead
On each project above a set size, a member of the group other than the project lead will be named alternatives lead for the concept phase, responsible for developing at least one substantially different option and presenting it at the first design review. The role will rotate, with priority given to engineers who rarely present. This builds the elaboration that research describes into the project structure. The roundabout case shows the value: a different option surfaced only because a senior engineer overheard a conversation. With an alternatives lead, such ideas would have a formal path.
Practice Five: Credit and Visibility
Two practices address who gets credit and visible work. Review notes will record who raised each comment that leads to a design change, creating a credit log that also feeds the comparison of outcomes described in Module 2. And client presentations will be paired: each public meeting or council presentation will be led by a senior engineer and a co-presenter from the group, rotating so that every engineer presents at least once a year. Module 1 found that five senior engineers led 24 of 31 presentations, and that internationally trained engineers led none. Pairing builds skills and visibility without leaving anyone alone in front of a critical audience.
Costs and Concerns
The practices are not free. The pre-read window adds about a day to the review schedule, the remote facilitator role takes one person's attention in each meeting and the alternatives lead adds roughly eight to twelve hours to the concept phase of a larger project. Senior engineers raised two concerns when I described the plan: that a fixed speaking order would slow reviews, and that paired presentations might put a less experienced engineer in front of a difficult city council. Both are fair. The pilot will time reviews before and after the change, and paired presenters will rehearse with their senior partner and handle the parts of a presentation suited to their experience, such as explaining a technical analysis they led. If reviews grow much longer, the speaking order can be limited to the major design elements.
My Role as Leader
Practices work only if the leader models them. I will attend reviews regularly, thank people by name when their comments change a design, ask follow-up questions of quieter members and avoid stating my own view before others have spoken. When senior engineers dismiss a comment quickly, I will ask them to explain their reasoning, so that disagreement becomes a discussion rather than a verdict. I will also meet individually with the five internationally trained engineers to ask what would make reviews and presentations easier for them, since the survey cannot capture specifics.
Pilot and Measures
The practices will be piloted for three months on all design reviews, with a short check-in with the group after each month. Four measures will show whether they work: the share of review speaking time held by junior and remote engineers, observed as in Module 1; the number of written comments per review and the share leading to design changes; the number of client presentations led or co-led by engineers outside the senior group; and the survey item on comfort disagreeing in reviews, which was at 45 percent agreement. The full inclusion scale will be repeated after six months. Results will be shared with the whole group at the end of the pilot, including anything that did not work.
Conclusion
Research shows that groups miss unshared information and that leader inclusiveness raises lower-status members' willingness to speak. The design group will respond with a pre-read and written comment window, a speaking order that starts with junior engineers, a remote facilitator, an alternatives lead, a credit log and paired client presentations, supported by my own behavior as leader. A three-month pilot and four measures will test the practices before Module 4 turns to handling the disagreements they are likely to produce.
References
Mesmer-Magnus, J. R., & DeChurch, L. A. (2009). Information sharing and team performance: A meta-analysis. Journal of Applied Psychology, 94(2), 535-546. https://doi.org/10.1037/a0013773
Nembhard, I. M., & Edmondson, A. C. (2006). Making it safe: The effects of leader inclusiveness and professional status on psychological safety and improvement efforts in health care teams. Journal of Organizational Behavior, 27(7), 941-966. https://doi.org/10.1002/job.413
Stasser, G., & Titus, W. (1985). Pooling of unshared information in group decision making: Biased information sampling during discussion. Journal of Personality and Social Psychology, 48(6), 1467-1478. https://doi.org/10.1037/0022-3514.48.6.1467
What the DIV 5003 Module 3 instructions ask for
The third DIV 5003 paper usually asks you to design inclusive collaboration practices for meetings and projects in your team or organization. Expect to propose specific, practical changes to how work is done together, not general commitments to inclusion. Most prompts want each practice justified with research and linked to problems you identified in earlier modules. Many also ask how leaders will model the practices and how you will know whether they work. Consider people who work remotely, in a second language or at lower levels of seniority. Plan a pilot or rollout with measures, and cite research on group decision making or inclusion in APA. Explain what each practice costs in time. Include remote staff.
How this DIV 5003 Module 3 example is built
Three studies open the sample: experiments showing groups neglect unshared information, a meta-analysis on information sharing and research on leader inclusiveness. Five practices follow, each linked to a case or finding from earlier modules: a two-day pre-read with drawing comments, a speaking order from junior to senior, a rotating remote facilitator, an alternatives lead for larger projects and a credit log with paired client presentations. A leader section describes specific behaviors, including holding back opinions. A three-month pilot with four measures, including speaking time and comfort disagreeing, completes the design. Costs in meeting time are weighed against benefits. The leader's own habits are part of the plan.
Where the points sit in the DIV 5003 Module 3 rubric
Collaboration practice papers are graded on specificity and justification. Instructors look for concrete practices that change how meetings and projects run, each supported by research and tied to problems found earlier. Attention to people who face particular barriers, such as remote or junior staff, earns credit. The leader's own behavior should be part of the plan. A pilot with measures shows the practices can be tested and refined. Generic inclusion statements, practices unconnected to evidence and plans with no way to judge success tend to lose marks. Each study used needs its APA 7 citation. Considering the time cost of new practices shows realism. Plans for remote staff help.
Common DIV 5003 Module 3 mistakes, and how to avoid them
Inclusive practices are easy to describe in general and hard to make specific. If you are unsure which practices fit your team's meetings and projects, how to justify them with research or how to measure their effect, we can help. Share what you learned about your team in earlier modules and the assignment guidelines; our writer will design practical collaboration changes tied to your findings, with a pilot and measures. Engineering, clinical, education and office teams all fit this assignment. Practice designs for your team are typically ready in two days. Each practice comes with the reason it should work and the measure that would show it does.
Write yours, or have the desk draft it
This paper is an original model document written by our desk, not a submitted student paper and not an official American College of Education document. Read it for the moves, then write your own to the instructions in your classroom. If you want one built to your exact prompt and rubric, the first custom sample is free and arrives in 24 to 48 hours.
More DIV 5003 and M.S. in Organizational Leadership sample papers
- DIV 5003 Module 1: Measuring Workplace Belonging
- DIV 5003 Module 2: Perspectives and Innovation
- DIV 5003 Module 4: Handling Disagreement Well
- DIV 5003 Module 5: Inclusive Communication Strategy
- DIV 5013 Module 4: Authenticity and Respect Review
- ORG 5013 Module 2: Collaboration Tool Selection
- DATA 5013 Module 4: Focus Groups and Coding
- DATA 5013 Module 2: Research Design and Sampling
DIV 5003 Module 3 questions, answered
What does DIV5003 Module 3 usually ask for?
Module 3 of DIV5003 usually asks you to design inclusive collaboration practices for meetings and projects in one team, grounded in research and earlier findings.
Why do groups overlook information only one member has?
Experiments show groups tend to discuss what everyone already knows and neglect unshared information, even when it would change the best decision.
Why let junior team members speak first?
Hearing senior opinions first tends to anchor others' views or silence them; reversing the order lets less experienced members share observations before a direction is set.
Where can I find a free DIV 5003 Module 3 sample paper?
This page has one: inclusive design review practices for a Sacramento engineering group, including written comment windows, juniors-first speaking order, a remote facilitator and paired presentations.
How should a leader support inclusive meetings?
Invite quieter members by name, hold back their own view until others speak, credit contributions publicly and ask senior members to explain quick dismissals.