Showing posts with label Reporting. Show all posts
Showing posts with label Reporting. Show all posts

August 31, 2017

VICE News Superior

So I have started watching VICE News and you should too. 

It is on HBO and is superior to the other big news outlets in so many ways. 

The intensity and clarity of their photography and videos is unbelievable!

My daughter said to me:
"This is clearer than REAL life!"

And she was right...I don't know how they do it. 


Also, they remove all the clutter from the news screen that CNN, MSNBC, and others use at the top and bottom of the screen--instead it's just clean, focused, and right to the news point. 

VICE puts the key messages in callouts right on the screen in large and easy to read boxes--the impact is you see the visual and the print message dramatically together and you get it and remember it!

They do this for their photos and videos.

Finally, with all the "talk is cheap" news these days, it is nice that VICE seems to focus more on reporting and less on subjective opinion. 

With all the failing, fake, and alternative news out there, it is nice to see that someone has invented a better news program.  ;-)

(Source Photo: Vice News)
Share/Save/Bookmark

November 4, 2014

Stop Sexual Assault

Saw this poster coming off the Metro today in Washington D.C. 

"It's on all of us to stop sexual assault."

It reminded me of this article I read in the DailyMail about this father of a 14-year girl in India that was raped in her home by a medical supply salesman. 

The young girl was raped and impregnated by a 45-year old man who boasted that he was "too well-connected" to ever be prosecuted. 

After some time passed, the father invited the rapist to dinner!

The rapist came. 

The father overcame the rapist, and repeatedly burned the man's genitals with hot thongs.

The rapist died.

This one rapist will certainly not be doing this again. 

While blatant violation of the law and vigilantism is not okay, the poster is right that we need to "stop sexual assault."

Statistics in this country are that 20% of college women are sexually assaulted before they graduate. 

Unacceptable!

Laws protecting women (and men) from sexual assault need to be strengthened, penalties stiffened, and we all need to be on the lookout for inappropriate behavior and speedily report this to law enforcement.

And no one should be above the law and basic morality. 

"It's on us."  

(Source Photo: Andy Blumenthal)

Share/Save/Bookmark

October 12, 2012

Cloud $ Confusion

It seems like never before has a technology platform brought so much confusion as the Cloud.


No, I am not talking about the definition of cloud (which dogged many for quite some time), but the cost-savings or the elusiveness of them related to cloud computing.

On one hand, we have the Federal Cloud Computing Strategy, which estimated that 25% of the Federal IT Budget of $80 billion could move to the cloud and NextGov (Sept 2012) reported that the Federal CIO told a senate panel in May 2011 that with Cloud, the government would save a minimum of $5 billion annually.

Next we have bombastic estimates of cost savings from the likes of the MeriTalk Cloud Computing Exchange that estimates about $5.5 billion in savings so far annually (7% of the Federal IT budget) and that this could grow to $12 billion (or 15% of the IT budget) within 3 years, as quoted in an article in Forbes (April 2012) or as much as $16.6 billion annually as quoted in the NextGov article--more than triple the estimated savings that even OMB put out.

On the other hand, we have a raft of recent articles questioning the ability to get to these savings, federal managers and the private sector's belief in them, and even the ability to accurately calculate and report on them.

- Federal Computer Week (1 Feb 2012)--"Federal managers doubt cloud computing's cost-savings claims" and that "most respondents were also not sold on the promises of cloud computing as a long-term money saver."

  - Federal Times (8 October 2012)--"Is the cloud overhyped? predicted savings hard to verify" and a table included show projected cloud-saving goals of only about $16 million per year across 9 Federal agencies.

  - CIO Magazine (15 March 2012)--"Despite Predictions to the Contrary, Exchange Holds Off Gmail in D.C." cites how with a pilot of 300 users, they found Gmail didn't even pass the "as good or better" test.

- ComputerWorld (7 September 2012)--"GM to hire 10,000 IT pros as it 'insources' work" so majority of work is done by GM employees and enables the business.

Aside from the cost-savings and mission satisfaction with cloud services, there is still the issue of security, where according to the article in Forbes from this year, still "A majority of IT managers, 85%, say they are worried about the security implications of moving to their operations to the cloud," with most applications being moved being things like collaboration and conferencing tools, email, and administrative applications--this is not primarily the high value mission-driven systems of the organization.

Evidently, there continues to be a huge disconnect being the hype and the reality of cloud computing.


One thing is for sure--it's time to stop making up cost-saving numbers to score points inside one's agency or outside.

One way to promote more accurate reporting is to require documentation substantiating the cost-savings by showing the before and after costs, and oh yeah including the migration costs too and all the planning that goes into it. 

Another more drastic way is to take the claimed savings back to the Treasury and the taxpayer.

Only with accurate reporting and transparency can we make good business decisions about what the real cost-benefits are of moving to the cloud and therefore, what actually should be moved there. 

While there is an intuitiveness that we will reduce costs and achieve efficiencies by using shared services, leveraging service providers with core IT expertise, and by paying for only what we use, we still need to know the accurate numbers and risks to gauge the true net benefits of cloud. 

It's either know what you are actually getting or just go with what sounds good and try to pull out a cookie--how would you proceed? 

(Source Photo: Andy Blumenthal)

Share/Save/Bookmark

December 16, 2009

Project Failure, Why People Can’t Own Up

I saw this funny/sad Dilbert cartoon on project management by Scott Adams (BTW, he’s terrific!).

It goes like this:

Office colleague (water cooler talk): How’s your project coming along?

Dilbert: It’s a steaming pile of failure. It’s like fifteen drunken monkeys with a jigsaw puzzle.

New scene….

Boss: How’s your project coming along?

Dilbert: Fine.

END

This common work scenario is sort of like a game of truth or dare: you either have to tell the project truth or take the dare and do something embarrassing like proceed with the project that isn’t on track.

Teammates, colleagues, peers often talk frankly and honestly about the problems with their projects and often the talk may become sarcastic or even somewhat cynical, because they know that they can’t tell their bosses what is REALLY going on.

What a shame in terms of lost opportunities to communicate, solve problems, and drive project success for the organization.

People are afraid to be honest, direct, tell the truth, and work together with their management on constructive solutions.

Instead, people simply say everything is fine, period.

Sort of like when your boss asks politely at work how are you doing? And rather than say, well I woke up late, missed my train, spilled coffee on my tie, and am having trouble meeting my deadlines this week, the person almost always replies, reflexively, “I’m fine” and “How are you?”

Another manifestation of the it’s fine syndrome is with executive dashboards or project scorecard reviews where virtually all the metrics show up as “green”, even when you know they are not—does yellow or red sound too scary to have to put on paper/screen and explain to the boss.

We are conditioned NOT to talk casually or to report to our superiors about issues, problems, or anything that can be perceived as negative, least they be labeled as trouble-makers or “the problem,” rather than the solution. Ultimately, employees don’t want to be blamed for the failures, so they would rather hide the truth then own up to the project issues, and work constructively with their management on solutions or course correction—before it’s too late.

Now isn’t that a novel idea? Management and staff working together, actually identifying the issues—proactively and in forthright manner—and working together to resolve them, rather than sitting across the table, sugar-coating or pointing the accusatory finger.

People have to take responsibility and own up when there is a problem and be willing to talk about them with their management, and management needs to encourage frankness, a “no surprises” culture, and a team-collaborative environment to solving problems rather than instilling fear in their employees or implicitly or explicitly communicating that they only want to hear “good news.”

Good news is not good news when it’s fabricated, a distortion, or a complete sham.

A culture of teamwork, collaboration, honesty, and integrity is the underpinning of project success. If everything in the project “is fine”, it’s probably not.


Share/Save/Bookmark