Twenty-three comments, a row apiece in the sixth MGMT 8910M week: the note quoted, the decision taken, the change and where it landed, and each other chapter it reached. Searches like "mgmt 8910m week 6 assignment example", "mgmt8910m week 6 sample" and "mgmt 8910m week 6 example" land here.
What a finished MGMT 8910M Week 6 feedback log looks like
Three to four pages, nearly all of it a log table. Columns give an identifier, the reader, the location, the comment quoted exactly, a decision of accept, adapt or decline, the change made with its new page reference, and a ripple column. Fourteen comments were accepted as written, six adapted and three declined. The ripple column carries the log's most important entry. The chair asked that work engagement be defined as a state rather than a trait, following Schaufeli and colleagues, who describe engagement as a state of vigor, dedication and absorption. Accepting that note in chapter one meant the instrument description in chapter three, still in draft, had to be checked for trait language, and the log records that it was and where it changed. Each declined comment carries a reason one sentence long.
How a MGMT 8910M Week 6 example is structured
Rows run in the order comments were received, not in order of importance, so the log doubles as a record of when each decision was made. Within each row the reading moves left to right, from what was said to what it caused, which is the direction the week asks the author to account for. Declined comments stay in the table rather than disappearing, each with its reason, because a note that vanishes without a word reads to the reader who wrote it as a note ignored. After the table, a short summary counts the decisions and lists every ripple the log triggered, grouped by the chapter it reached. The summary closes with the two comments whose changes are not yet complete, each assigned to a week on the writing plan so that neither drifts.
Every comment quoted
Notes appear in the reader's exact words, not the author's summary of them. A paraphrase tends to shrink a comment toward the fix the author already preferred, and the chair checking the log will notice.
Accept, adapt, decline
Three decisions cover every row. Adapt is used when the concern is accepted but the proposed fix is not, as when the second member asked for a new subsection and the author answered the same concern in two existing paragraphs.
The ripple column
A change in one chapter can contradict another written earlier or later. When engagement became a state, the log sent the author to chapter three's instrument description, and the entry records the check and the sentence it altered.
Declines with reasons
Three comments were declined. One asked for a second theoretical framework; the log explains that servant leadership, the concept Greenleaf introduced, already carries the study's argument, and that adding a second framework would split the analysis without sharpening it.
Open changes, scheduled
Two accepted comments require work not yet done. Rather than marking them resolved, the log assigns each to a week on the writing plan, so the promise made to the reader has a date attached.
Where marks go in MGMT 8910M Week 6
Faculty read the log for consequences, not courtesy. A table of comments answered with thanks or addressed, and no page reference, records acknowledgment and nothing more, which sits low on nearly any rubric. Credit rises with the specificity of the change column: a new page reference for each accepted comment lets the reader verify the work in seconds. The ripple column shows doctoral control of a long document most clearly, and a log that treats every comment as local to its chapter misses the point of the week. Declines are judged on their reasons rather than their number; a decline with a sound argument often earns more than a grudging acceptance. Open items scheduled on the plan earn credit that items marked done prematurely lose.
Get a MGMT 8910M Week 6 example written to your instructions
Forward the Week 6 prompt and rubric and describe the kinds of comments your chapters drew, paraphrased if you prefer. A log with decisions, page references and a ripple column is ready within 24-48h, with no fee for the first. Its twenty-three notes answer an invented study; deciding what your own readers' comments require is left with you.
MGMT 8910M Week 6 questions, answered
Is it acceptable to decline a committee member's comment?
Yes, when the log gives a reason a reasonable reader could accept. Committees generally expect some disagreement from an author who understands the study, and a reasoned decline shows that understanding. What damages trust is a comment silently left unaddressed. If the comment concerns a requirement rather than a judgment call, such as a program format rule, declining is not an option.
What is a ripple, and why track it?
A ripple is any place outside the commented passage that a change forces the author to revisit. Definitions, constructs and the research question appear in several chapters, and changing one instance leaves the others disagreeing. Tracking ripples in the log turns that risk into a checklist. Without it, contradictions accumulate quietly and surface months later, often during a full committee read.
Should minor comments like typos go in the log?
Grouped, not individually. A single row can note that sixteen mechanical corrections were made throughout chapter two, which keeps the table readable and focused on comments that change the argument. Listing every comma inflates the log and buries the entries a chair actually wants to verify, such as a changed definition and the places it reached.