First Week Review

Week One Theme: Learning the language of Organizational Behaviour without losing sight of the worker inside the system.

Opening Reflection

The first week of MGT2382 did not begin with fireworks.

It began with friction.

Some of that friction came from the textbook language. Some of it came from trying to translate course concepts into my own experience. Some of it came from the fact that Organizational Behaviour, at least in its opening chapter, can feel dry before it starts to feel useful.

But by the end of the first week, a pattern had started to emerge.

This course is not only about management theories, workplace definitions, or academic models. It is about what people think, feel, and do inside organizations. It is about how pressure moves through systems. It is about how norms, values, roles, communication, leadership, accountability, and human limits shape what actually happens at work.

That is where the course started to connect.

Not because the material was exciting on its own, but because it gave language to things I have already watched happen in real workplaces.

The First Learning: I Am Not Starting From Zero

One of the strongest realizations from the first week is that I am not starting from zero.

When the course introduced terms like norms, values, human capital, stakeholders, open systems, multiple levels of analysis, and evidence-based management, my first reaction was not always academic. My mind went to lived experience.

When the assignment mentioned norms and values, my first thought went back to sociology: mores, folkways, shared expectations, and social rules. But in the Organizational Behaviour context, norms and values seemed more practical. They are not only abstract ideas. They are the operating rules of a workplace.

Values are what the organization says it believes.

Norms are what people are actually expected to do.

That distinction matters.

An organization may say it values respect, wellness, flexibility, safety, teamwork, or communication. But the real test is not what appears in the policy manual. The real test is what behaviour gets rewarded, punished, tolerated, ignored, or quietly expected.

That became one of the major threads of the week.

Norms, Values, and the Danger of Bad Standards

The first journal entry connected norms and values to standard operating procedures and ISO-style systems.

That connection matters because standards can be useful. People need shared expectations. Teams need consistency. Organizations need procedures that make work repeatable and understandable.

But standards can also trap people.

If a bad process becomes the approved process, then the organization may repeat the same mistake over and over because the procedure itself has become protected. In that case, the system is no longer serving the work. The work is being forced to serve the system.

That is a major Organizational Behaviour issue.

It connects to responsibility without authority. It connects to evidence versus shame. It connects to conflict that is blamed on personality when the real problem may be structural.

The first week made this point clear: organizations need shared rules, but those rules also need review, correction, and room for evidence.

The Textbook Was Dry, But the Definitions Were Useful

The Chapter 1 reflection was blunt: the textbook did not hook me right away.

That still feels true.

But even dry material can contain useful tools.

The definition of Organizational Behaviour as the study of what people think, feel, and do in and around organizations is useful. It keeps the subject grounded in actual human behaviour, not just organizational charts or management slogans.

The definition of an organization as a group of people working interdependently toward a purpose is also useful. The word interdependently matters. It means organizations are not just individuals doing separate tasks. They are systems of people tied together by expectations, resources, authority, communication, power, money, time, pressure, and consequences.

That connects directly to the larger lesson of the week:

You cannot always understand a workplace problem by looking only at one person.

Sometimes the individual made a mistake.

Sometimes the team norm is unhealthy.

Sometimes leadership created confusion.

Sometimes communication failed.

Sometimes the structure does not match the responsibility being placed on people.

Usually, more than one level is involved.

Employees Are Stakeholders, Not Just Resources

Another major theme this week was the employee as stakeholder.

The course material discusses human capital: the knowledge, skills, abilities, creativity, judgment, and experience employees bring to an organization.

That language is technically useful, but it is incomplete if it stops there.

Employees are not only resources.

They are not only inputs.

They are not only carriers of skill.

They are people with bodies, bills, families, stress responses, hopes, limits, and breaking points.

This became even clearer in the later reflections on sickness, accountability, and attribution. The phrase that kept returning was simple:

Human capital still has a body.

That may become one of the most important takeaways from week one.

Organizational Behaviour cannot treat people as abstract performance units. If it does, it misses the human reality underneath the role.

The Body Is Not a Breach of Character

The sick-day reflections brought the course material into real life.

A missed shift, a late arrival, or a sick day can create real impact. Someone else may have to cover. Work may be delayed. A team may be strained. A client may still expect the service to be completed.

That impact matters.

But impact is not the same as intent.

This became a key distinction during the week. There is a difference between saying:

“Your absence created a problem.”

and saying:

“Your absence proves something bad about you.”

The first names impact.

The second assigns character.

That is where Organizational Behaviour becomes practical. It gives language to attribution, role pressure, team strain, workplace norms, and the way conflict escalates when people turn a practical problem into a moral indictment.

The cleaner lesson is this:

Accountability does not require shame.

A person can own the impact of their actions without accepting a false identity as lazy, dirty, selfish, unreliable, or defective.

That distinction matters in workplaces. It also matters in any system where people are expected to perform under pressure.

Multiple Levels of Analysis in Real Time

The sick-day situation also showed why multiple levels of analysis matter.

At the individual level, one person was sick and could not fully meet the schedule.

At the interpersonal level, another person felt frustrated, unsupported, or left alone with extra work.

At the team level, coverage was thin enough that one absence created a serious burden.

At the organizational level, there may not have been enough backup, communication structure, or contingency planning.

At the stakeholder level, the client still expected the work completed, the company still had a contract to protect, and employees were caught between service demands and human limits.

That is Organizational Behaviour in the wild.

The easy explanation is to blame one person.

The better explanation asks what conditions surrounded the behaviour.

Client, Employer, and Role Confusion

The “Don’t Make the Client Your Confidant” reflection added another practical workplace lesson.

In third-party service work, the employee can end up standing between two worlds: the employer and the client.

The client sees the work. The client may complain. The client may praise. The client may feel like the real boss because they are physically present.

But the client is not usually the employee’s employer.

That creates role confusion.

The key lesson was not “hide everything from the client.” The lesson was about channels, authority, and protocol.

If the problem is a coworker issue, a supply issue, a scheduling issue, a training issue, or a management issue, the first question should be:

Who actually has the authority to fix this?

Psychological safety matters. Employees should be able to speak up about concerns. But psychological safety does not mean every audience is the correct audience.

Venting to the client may feel relieving in the moment, but it can turn an internal workplace problem into a contract problem. It can weaken the client’s confidence in the employer. It can expose the employee. It can make a real concern harder to resolve.

The better move is to identify the issue, identify who has authority, use the internal channel first, document without dramatizing, and escalate intentionally when the risk demands it.

Work-Life Integration or Boundary Collapse?

The work-life integration reflection was another strong point in the week.

The course material introduced work-life integration as a way of understanding how employees participate in both work and non-work roles. That concept has value. People are not machines. They do not stop being parents, students, caregivers, spouses, homeowners, patients, neighbours, or human beings just because they are employees.

But the language of integration can become dangerous when it is used badly.

Healthy integration gives people flexibility, autonomy, and some control over how work fits into life.

Unhealthy integration becomes boundary collapse.

If employees are expected to answer emails after hours, pick up the phone when the boss calls, monitor messages during family time, respond while sick, or treat silence as lack of commitment, then the organization is not practicing integration. It is practicing access.

That connected directly back to norms and values.

A company may claim to value wellness, family, flexibility, and mental health. But if the real norm is constant availability, then the real value is not wellness.

The real value is access.

The right to disconnect belongs in this discussion because it forces organizations to confront the boundary between work and life. Even where the law or policy is limited, the concept matters because it asks whether employees are respected as whole people or only valued when they are useful.

Organizations as Systems

By the end of the week, the course material had moved from individual definitions into systems thinking.

The Six Systems frame — leadership, communication, accountability, delivery, performance, and measurement — helped organize much of what the earlier reflections were already circling.

Leadership sets context.

Communication shapes clarity.

Accountability connects expectations to consequences.

Delivery turns promises into actual service.

Performance depends on people, resources, skill, development, and retention.

Measurement tells the organization whether it is on track or lying to itself.

The important insight is that these systems do not operate separately. When one fails, pressure moves into the others.

Poor leadership damages communication.

Poor communication weakens accountability.

Weak accountability affects delivery.

Poor delivery creates performance issues.

Poor measurement may prevent the organization from even understanding what went wrong.

This tied the whole week together.

Organizational Behaviour is not just about individual attitude. It is about the conditions people are placed inside.

Communication Is Infrastructure

Another strong first-week conclusion is that communication is not decoration.

Communication is often treated like a soft skill, but inside an organization it functions more like infrastructure. It determines whether people understand expectations, whether problems are surfaced early, whether mistakes can be discussed, whether clients receive consistent service, and whether workers know what to do under pressure.

Bad communication is not just unpleasant.

It creates operational risk.

This connects to almost every post from the week. Sick-day conflict involved communication. Client-confidant problems involved communication channels. Work-life integration involved after-hours communication norms. Leadership systems involved strategic communication. Norms and values were revealed through what people actually said, tolerated, expected, or punished.

Communication is where culture becomes visible.

First Week Personal Takeaway

My personal takeaway from week one is that MGT2382 may be more useful than it first appeared.

I am still not in love with the textbook style. I am still not pretending dry academic language is suddenly thrilling. But I can already see the tools buried inside it.

The course is giving me a vocabulary for things I have already been watching for years:

• responsibility without authority;
• employees treated as resources instead of people;
• systems that blame individuals for structural failures;
• norms that contradict stated values;
• communication breakdown under pressure;
• role confusion in third-party service work;
• accountability twisted into shame;
• work-life integration used as a cover for permanent availability;
• leadership systems that shape every other part of the organization.

That is not nothing.

That is a foundation.

What I Need to Watch Going Forward

Going into the next week, I want to watch for three things.

First, I need to keep translating the textbook language into lived workplace examples. That seems to be how the material becomes real for me.

Second, I need to be careful not to turn every concept into a personal essay only. The lived experience matters, but the course also requires clean academic framing. The goal is to bridge the two.

Third, I need to keep asking where the employee fits in the model. If a theory talks about performance, effectiveness, culture, or stakeholder value without seriously considering the worker, then I need to notice that gap.

Closing Review

Week one began with resistance.

It ended with connection.

The material is still dry in places. Some of the language feels built for white-collar workplaces more than frontline, service, cleaning, trades, or shift-based work. That is a limitation I will keep watching.

But the core ideas are useful.

Organizations are systems.

People behave inside conditions.

Norms reveal real values.

Communication shapes culture.

Accountability does not require shame.

Human capital still has a body.

Employees are stakeholders.

And a good organization should not only ask whether the employee succeeded.

It should also ask whether the system made success possible.

That is where week one leaves me.

Still not fully hooked.

But paying attention.

Godspeed.