Making Assumptions

One of the many things I have learned in my illustrious career is to assume nothing.  It is poison to development and open collaboration.  Question and gather facts instead.  That enables one to make decisions rather than simply passing judgement.

A colleague continually ignoring statements in favor of her own assumptions about process, procedure, and standard is dangerous to business continuity at best.  It is toxic to collaboration.

As regards the above image.  It helps to listen to the answers too.

What happens when you make an assumption?

Self-Service Confidence

She did it again.  The moment nobody was around, she put on her favorite attitude.  We were discussing self-service points.  I lightly laughed at an assumption she had made and began to explain how we were obviously misunderstanding one another, and she immediately fired across the bow, "I did not think it was funny."

I fired back, "I never said it was."

She quickly dropped back into trying to tell me how wrong I was.

As quickly, I began explaining again how it was only a mutual misunderstanding, attempting to explain the difference another way.

She seems to have self-confidence issues.  This only happens when nobody else is looking.  Otherwise, she is all smiles and laughter.

Hypocrite.

Kudos from COO

Todd is always willing to listen to my requests for new/different/improved data and dashboards and help me out with any project I'm working on. His willingness to jump into these projects with me has made the world of difference this last year in my ability to make decisions which improve the programs. Thanks Todd!!

Innovation

If your employees are not coming to you with ideas for improvements to your business, you are not inspiring them and your company is not growing.  You will fail.

Tech Sucks Sometimes

Technology was supposed to make our lives easier.  It seems like, more often than not, it just pisses me off.

And, what happened to the promise of more free time to pursue other interests.

It is all a lie.

Kudos from CAPO

Todd discovered an anomaly in [The Firm] data that was able to be corrected, saving [The Firm] funds.

Miscoding Payroll

In reviewing data inconsistences produced by a Power BI report, which had been thus far consistent, a coding problem was uncovered that identified employees paid for Differential Time and Differential Overtime that should have been Regular Time or Regular Overtime.  The problem relates to approximately 5000 hours or about $100k over 6 months.

Solution Provider Can't Handle It

Our solution provider got a little upset because we wanted to include so many IP addresses for access to the External Data Feed.

We intended to use Power Automate to SFTP and extract that external data.

We originally only provided 2, and then all of Microsoft's Power Platform IPs, which were only 20 or so.

After speaking with their CIO, they denied the request.  Too many IPs.

Silly.  Stupid. Lazy.

Stories from Vegas

Made it out to Las Vegas for the first time since I was probably 5 years old.  To be perfectly honest, it may very well be the last trip to that world.  I was not all the impressed.  If you do not gamble or drink excessively, what exactly is there for you?

A lot of conferences are held there though, which is what got us into this mess.  Hyland Software and then Microsoft.  Most of the photos are relegated to my other site, in multiple articles.

power platform conferencing (phocas.net)

vegas forum pub quiz (phocas.net)

carly rae jepsen and microsoft (phocas.net)

vegas casino royale style (phocas.net)

thursday mat franco (phocas.net)

a freemont street experience (phocas.net)

closing out at omnia (phocas.net)

cosmopolitan meadows art (phocas.net)