DMAC topic

[Stan]

I am ready to start the DMAC project and have read through the instructions, but I am having trouble coming up with a project that isn't too 'technical'. I only have a few years experience in Health so most of my projects have been quite technical. Has anyone tried writing about a topic that was completely made up? (the instructions say this is ok to do).

Also, has anyone submitted a paper that can be considered technical but passed by focusing on the decisions/communication that was involved in the situation?

I am struggling here.

[LoneGirl]

I am ready to start the DMAC project and have read through the instructions, but I am having trouble coming up with a project that isn't too 'technical'. I only have a few years experience in Health so most of my projects have been quite technical. Has anyone tried writing about a topic that was completely made up? (the instructions say this is ok to do).

Also, has anyone submitted a paper that can be considered technical but passed by focusing on the decisions/communication that was involved in the situation?

I am struggling here.

My project was based on a real project I had done, but the part I had done would have been considered too technical. So I expanded it to take into consideration how my piece was part of a larger project affecting other areas (like the administration area, the overall profit of the company, etc). For any parts that I didn't have real knowledge of or data on, I made up. I think a good way to keep from being too technical is to consider how your decision could affect multiple areas/aspects of the company.

[aslyck]

Yeah, I agree with LoneGirl.

I'd base in on a real project, so you can throw in some charts and data, but add some conflict to it. How will the decision affect the policyholders, CFO, CEO, the board, IT department, legal, etc? There's bound to be someone with a conflicting viewpoint and you can make up that part.

[makhatri01]

Yeah, I agree with LoneGirl.

I'd base in on a real project, so you can throw in some charts and data, but add some conflict to it. How will the decision affect the policyholders, CFO, CEO, the board, IT department, legal, etc? There's bound to be someone with a conflicting viewpoint and you can make up that part.

Are graphs and charts necessary?? I made up a case in my head and started expanding on the idea. Obviously I considered a couple of possible solutions but through reasoning I dropped the rest out. I have been describing the process and procedure that was used to come to the solution and then finally the execution process. I considered the implications of the decision on several stakeholders and how their interests were taken care off. I have briefly talked about the key responsibilities given to individuals within the company and ideas we got from them. Is there anything I am missing here or is there anything that should not be a part of the project? The concept I am talking about is fairly technical, but the problem solving procedure is fairly straightforward and simple. I haven't taken any numbers, just mentioned a few that were a part of the final approved solution. Any experienced people in DMAC, your input is much appreciated!!