Nearly a month after first detecting a potential identity theft when reviewing my credit reports, I’m frustrated by the lack of progress despite my efforts. A recent email from Experian, the credit bureau that seems to be the source of my problems, highlighted the company’s refusal to remove what I believe is the root cause record on my report. Just when I thought I was entering the final phase of cleaning up my credit report, I came to realize that I’m probably just getting through an early chapter in what will be a much longer story.
Sunday, February 23, 2014
Saturday, February 15, 2014
Identity Theft: Proof that Life is not Fair
I spent a weekend fuming over the fact that my credit reports from two bureaus showed a fraudulent collection from Dish Network and several personal information entries that listed names, addresses, and phone numbers on my report that were not mine. There were several possibilities for the entries: 1) The bureaus screwed up; 2) Someone fat-fingered my social security number when providing credit for Dish Network service; 3) Someone had fraudulently used my social security number. No matter how little control I had over the initial event, if I wanted clean credit reports, I knew that no one was going to help me out.
Sunday, February 2, 2014
Identity Theft: Guilty Until Proven Innocent
“What is your identity?” It’s more than just an existential question, it’s a question that you need to ask yourself when addressing a potential identity theft situation. To be more precise, you have to ask yourself, “What is it that identifies you?” To begin the recovery process once you detect an identity theft, something that I discussed recently in relation to my own issue, you have to be able to provide documentation that assures everyone involved that you are who you say that you are. Perhaps even more important is the inverse, that you need to be able to show that you aren’t who you say you aren’t.
Friday, January 31, 2014
Federal Contracting Part 4: Intervention and Rehab
The challenge faced by HHS and CGI Federal to build Healthcare.gov were exceptional. They attempted to tackle an extremely complex data integration and communications platform in the relatively short timeframe of just under two years. Even without the highly charged political environment that hovered over the project, threatening to rain down at every moment, I would consider the project to be as ambitious as any government IT project has been. Add to that the directives and regulations that the project had to be managed against and I would have though initial success to have been an improbable expectation.
Monday, January 27, 2014
A Victim of Identity Theft?
I believe that I am the victim of identity theft.
At first, I didn’t think much of it. Perhaps my understanding of how personal data flows and security drove me to discount what it was I was seeing as “really no big deal.” Or, maybe I have become so cynical about how the definition of identity theft has expanded to include acts that I wouldn’t naturally consider a “theft” that I disregarded the event. Whatever the root cause of my denial, I’ve moved on. It’s time to deal with the problem and I plan to share my experiences every step of the way.
Sunday, January 26, 2014
Federal Contracting Part 3: The Definition of Madness
There is a common assumption in government IT services procurement that past experience is an indicator of future success. But, when working with an industry that benefits mostly from the efforts of individual performers, the idea of ‘corporate’ past experience is a logical fallacy. Not only does it put the government at an immediate disadvantage, it favors repeating inefficient activities that benefit large contracting firms rather than promoting the innovation needed to move into new technology areas.
Wednesday, January 22, 2014
Federal Contracting Part 2: Good to be a Contracting Firm
This is Part 2 of my Federal IT Contracting series. Please be sure to check out my Introduction posting that includes a disclaimer about my past relationship with CGI Federal, the primary contracting firm responsible for the Healthcare.gov project.
My previous Federal IT Contracting posting presented a jarring insider analysis of how contracting firms realize success from failure. Some may interpret my analysis as a shot against contracting firms, illustrative of a tainted industry that deserves more oversight. With recent movements to reduce how much firm executives can earn despite very limited direct involvement on any customer-facing project, I admit to harboring some animosity towards those firms. But, having also served as an executive in a startup firm for several years, I submit that the government is far from blameless. That government managers often channel an insatiable childlike appetite for wants without really understanding what it is they need leaves them susceptible to failures like that currently embodied by Healthcare.gov.
My previous Federal IT Contracting posting presented a jarring insider analysis of how contracting firms realize success from failure. Some may interpret my analysis as a shot against contracting firms, illustrative of a tainted industry that deserves more oversight. With recent movements to reduce how much firm executives can earn despite very limited direct involvement on any customer-facing project, I admit to harboring some animosity towards those firms. But, having also served as an executive in a startup firm for several years, I submit that the government is far from blameless. That government managers often channel an insatiable childlike appetite for wants without really understanding what it is they need leaves them susceptible to failures like that currently embodied by Healthcare.gov.
Subscribe to:
Posts (Atom)