Journey to become a business analyst in health IT

https://www.infoq.com/articles/structured-conversations-mvp

A Harvard study shows that daily self reflection can help people to become better leaders. Self reflection in the sense of taking time to reflect on activities in the day, and figure what could have been improved to achieve a better outcome. This seems like an effective technique and I want to be on board. Things that I think can help me to be more effective at work - always have a mindset of contributing positively in a meeting - act, take ownership - connect, share your thoughts with others in attempt to make things better - read to improve vocabulary That's all I have for now. And also a link to an article worth remembering. https://www.quora.com/How-do-I-become-a-more-intelligent-person

I was very fortunate that my company sent me to San Francisco to attend the Health 2.0 2012 conference. I like the coastal city very much. The weather, the variety in culture, seafood and fleet show on the piers, Boudin sourdough... everything is vibrant and refreshing. I love seeing palm trees in the streets, it makes me feel like I am on vacation because of the tropical element it brings. Sketchy notes from conference: - aging population, chronic disease account for 75% of health care cost - 5 shifts in healthcare system reform Explode business model: revenue source, business structure, data workflow all shifts. Upgrade cost analysis: end cost shift competing with each other for funding, reallocate cost across network. Measure, improve, try, measure again. Build on smart primary care, reduce cost by keeping patient out of ER put a crew on it, not work in silos, integrate multi-disciplinary team, drive disk to operation level. Not paid by visit - better qual...

http://www.iag.biz/images/6_things_your_cio_needs_to_know.pdf This post startled me when it made me realized how complacent I've become of my skills. Having moved from giant corporate to an non-profit organization of less than 200 people, I became more and more comfortable with the slow pace, lack of any kind of evaluation on my work product. I noticed a number of problems in my company around requirements maturity: 1. People only look at pictures/mockups, and don't read any text. Therefore anything not in the picture is treated as a missing requirement. 2. Each business component, e.g. security and privacy should document highlevel system capability statements and then request for these features; not asking the business analyst to produce a list of detailed rules on application security and call that security requirements. 3. The company should invest in a requirements management tool so that different views of the requirements can be generated. This would save...

Making a Decision By Weighing Up Different Factors Also known as Decision Matrix Analysis, Pugh Matrix Analysis, and Multi-Attribute Utility Theory (MAUT) -------------------------------------------------------------------------------- http://www.mindtools.com/pages/article/newTED_03.htm#np

I keep forgetting to keep things simple, which is a fundamental discipline of business analysis. Before we dive into a process, we need to ask ourselves, what are we trying to achieve, what is the value added, and does the user experience make sense. We were going through an exercise of migrating users from an existing online application to another portal. A clean cut over can't be performed, so both websites need to be available, and the process we need would make users jump through hoops and bend our elbows backwards to support it. Both business users and technical people seemed determined to charge ahead with the plan despite of many loopholes that made me scratch my head. Our usability expert finally said something that everyone was contenmplating subconciously. What is the point of migrating if we are not ready to live with the consequences. The moral of the story is we shouldn't define a process just for the sake of have a process, we need to think whether it provides eff...