Where knowledge and industry meet...

BradM

Leader
Admin
I am wanting to write some papers for publication. However, I don't like writing junk just to write stuff. I like it to be interesting and useful.

What (in your experience) are some areas where you feel that there is a deficiency in knowledge? Maybe for example, requirements in the standards that are poorly understood.

Any input would be appreciated.
 

RoxaneB

Change Agent and Data Storyteller
Super Moderator
I am wanting to write some papers for publication. However, I don't like writing junk just to write stuff. I like it to be interesting and useful.

What (in your experience) are some areas where you feel that there is a deficiency in knowledge? Maybe for example, requirements in the standards that are poorly understood.

Any input would be appreciated.

I think the more applicable question is what are you passionate about? That's what your writing should focus on, centralizing around the 'why' a reader would be interested in reading about the topic.

Think about your posts here in the Cove or the topics that really energize you. You'll find your topic easily enough then. :cool:
 

BradM

Leader
Admin
I think the more applicable question is what are you passionate about? That's what your writing should focus on, centralizing around the 'why' a reader would be interested in reading about the topic.

Think about your posts here in the Cove or the topics that really energize you. You'll find your topic easily enough then. :cool:

Roxane, you know me well enough... my problem is I'm passionate about most all the subjects.

You do have a point, though. I think that my buttons, so to speak, get pushed more when Deming is completely ignored.

One of my FB friends boy signed up for the Navy (proud of him). He is maybe... 18 years old with less than a year in training. We find out he is in the hospital, nearly dead from electrocution. The details are kind of sketchy (hey.. it's FB :) ) but he was moving around some wires and there were some live 480VAC wires that got him. Then.. the individual with him tried to pull him off but she got shocked. But here's the thing, she didn't run or give up; she kept pushing him (at her pain) until he broke free. She saved his life. Heroism. :agree1:

Anyway, here is Process Brad (also Master Electrician Brad..) my head is about to spin off my body. Within three minutes I have at least 12 major points drawn out. (Oh... no supervision (against NEC Code), PPE, his training, her training, proper tools, why was it hot in the first place, etc.)

My friend's son post something like "hey yea... my CO said it wasn't really anybody's fault." Brad's head begins to spin again. I tried to keep from posting, but I couldn't help it. I said, Um yea it's somebody's fault: The CO.
That situation should have NEVER happened.

So I could look at Deming's philosophies and how they relate to Processes.

Any other ideas/suggestions are greatly welcome!
 

BradM

Leader
Admin
I see a lot of questions pertaining on how to incorporate risk into the QMS. That would be a relevant and helpful topic.

Thank you Miner. Specific topics like this are of interest.

So I think in the 2015 (and maybe the 2009) there were requirements for risk assessment and such specified in the ISO 9001 requirement. Correct? I don't have copies of them so I don't know. Does someone have the clause that is referenced?

So maybe how to define, classify, and develop processes for dealing with risk.
 

RoxaneB

Change Agent and Data Storyteller
Super Moderator
So maybe how to define, classify, and develop processes for dealing with risk.

A blog on "Risky Business" (okay, Tom Cruise or the production company might sue if you used that name) could be interesting if various perspectives were used.

  • Multiple levels - There's high level organizational/strategic risk and then there's design risks and then there's all the stuff in between. The tools used might vary depending on where the scope of the risk management lies.
  • Case Studies - Tell me a story! Similar to what you shared re: the Navy incident, case studies give us context and help us to see applicability. You could provide the scenario and then challenge the user to identify types of risks before including your own thoughts.
  • Specific standards - The requirements for risk management might vary between multiple standards. You could spend time on each standard before blending them together to show alignment/variance.
  • Various application points - Applying risk management to something new might take on a different approach than applying the concept(s) to something more mature.

At the end of the day, it's great if it's something you enjoy but it's even better if it engages others.

Resonating with your audience, making them want to pay attention...that needs to be your hook.

Slightly off topic, but it relates to the resonating with your audience point. When I facilitate a focus group, it's one thing to say "Hi, I'm Roxane and I'm from the corporate operations team. And you're all here because your supervisor...ahem...nominated you." If I was one of my organization's nurses and i heard that, I'd tune out pretty darn quick.

Instead, I want to form a bond with these nurses. Nurses are about caring and compassion and helping people feel good. So, I show a slide that is titled #HelloMyNameIs ... Roxane. And I explain the story behind #HelloMyNameIs. Since doing this, my focus groups have resulted in a lot more interaction and idea sharing, because suddenly I'm one of them, we have common interests, and there is the beginning of a bond of trust and understanding.

As for why they are there, I make it about them and their ability to help the organization (not just our clients) - I show 'Why' there are there, 'How' this can help, and 'What' they can do.

To blog simply for the case of blogging could eventually lead to disinterest - either on your part or the part of your readers.

PS...For those interested in the #HelloMyNameIs concept. Keep in mind that I now work in a not-for-profit, community healthcare provider, which could be why this resonates with our staff...

A young mother in England, who was also a nurse, was diagnosed with cancer. She went into remission and all was good until a few years later, she started feeling unwell again. She went and had multiple tests done. There she was, lying in her hospital bed, alone. Her husband wasn't in the room, neither were her young children. In walked a doctor she didn't recognize who picked up her chart and said "The cancer's spread." He then left the room. She was more upset by how the doctor had behaved than by the actual diagnosis. Her husband asked her what she was going to do about it and the #HelloMyNameIs campaign began. It's about healthcare professionals introducing themselves and forming some type of connection with the clients...patients are people, not simply sick bodies. Unfortunately, our young mother passed away, however her husband has kept up the campaign in her honour. And so...#HelloMyNameIs...Roxane.

Every time I tell people this story, and I've told more times than I can count, I get goosebumps. Something so simple yet so profoundly...human...saying hello.
 

BradM

Leader
Admin
Hmmm... I might have just found my co-author. :agree1:

I looked through some of the operations management journals and didn't see the topic of Risk addressed thoroughly. It certainly wasn't covered to the extent that ISO9001:2015 inbeds it in the standard.
 

RoxaneB

Change Agent and Data Storyteller
Super Moderator
Hmmm... I might have just found my co-author. :agree1:

I looked through some of the operations management journals and didn't see the topic of Risk addressed thoroughly. It certainly wasn't covered to the extent that ISO9001:2015 inbeds it in the standard.

Perhaps that's your attempt at writing...WHY isn't addressed or discussed as much as the other requirements? Is it presumed that organizations are already doing it but not the other requirements of the standard (because, yeah, the notion of metrics/indicators is sooooo new :rolleyes:)? Is it hoped that it will simply go away?
 

BradM

Leader
Admin
Perhaps that's your attempt at writing...WHY isn't addressed or discussed as much as the other requirements? Is it presumed that organizations are already doing it but not the other requirements of the standard (because, yeah, the notion of metrics/indicators is sooooo new :rolleyes:)? Is it hoped that it will simply go away?

Good questions, Roxane. I found some later journal articles on Risk. I'm going to start on them and see what they say.
 

Marcelo

Inactive Registered Visitor
Hmmm... I might have just found my co-author. :agree1:

I looked through some of the operations management journals and didn't see the topic of Risk addressed thoroughly. It certainly wasn't covered to the extent that ISO9001:2015 inbeds it in the standard.

It's not covered because it does not exist (or existed before in the way the standard addresses it). It was included in ISO 9001, but if you look at literature you will notice that it has never been part of quality engineering.
 
Top Bottom