Subscribe to This Blog | Author Login

Banking on Tomorrow
"tomorrow is promised to no one"
Amazon | CNN | Wikipedia | CEOExpress 
bleeding heart....

You are viewing an individual message. Click here to view all messages.

Carol H Tucker

Passionate about knowledge management and organizational development, expert in loan servicing, virtual world denizen and community facilitator, and a DISNEY fan

Contact Me
Subscribe to this blog

beladona Memorial

Be warned:in this very rich environment where you can immerse yourself so completely, your emotions will become engaged -- and not everyone is cognizant of that. Among the many excellent features of SL, there is no auto-return on hearts, so be wary of where your's wanders...

  Navigation Calendar
    Days with posts will be linked

  Most Recent Posts

Day 26

Today is the 5th day of the 4th week, the 26th day of the 1st month, and the 26th day 2023

A long long time ago, when I was a a small community bank undergoing a lot of organzational change, I started writing about the process and the personalities.  I christened the posts "As the Bank Turns" and it actuallly became rather popular reading.  When that community shut down, it migrated to its successor, and then eventuallly to the KM Wiki where I maintained a couple pages devoted to banking.  All was lost when that Wiki imploded, and we learned all too late that the backups we thought were being made had been distroyed by a server crash..

The past couple of days have me reminiscing about those posts, and mentally thinking how I would write up the comedy of errors that is happening in our small organization.  The problem? A ibt of background info first.  

IT, which is provided by one of our credit union equity owners, sets up the mobile phones for our company, keeping them under the blanket of their security protocols.  Because these company phones can be used to access the email accounts and the company files [both of which live on  the credit unions server, there is a lot of security on the phones that would not be on a normal phone.  About five years ago - yes that long ago -  IT started using a security protocol from a third party, an app that was installed on each phone and you had to log into every time you used your phone to get access to contacts, emails, calendars, et al.  Sounds simple enough, right?

Now the Presdient/Ceo/founder of my little company [who will henceforth be referred to as "bossman"] decides he doesn't want a seperate company phone like everyone else.  Having two phones doesn't make any sense to him when the company pays for the company phone and he can just use it for everything!  So he wants to keep only one phone, nnd IT obligingly loads the security app onto his personal phone.  Now bossman loves loves LOVES Samsung phones.  He always has had a Samsung and doesn't want an iPhone no siree.   Every other company phone in the organization is an iPhone, and the security app is an iPhone app, but he is bossman and IT is being obliging.   Through the years, bossman has had phone issues.  He can't get emails.  He can't open email attachments.  He can't upload pictures of property site visits.  His phone is slow.  The security app is stupid.  Visit after visit to the main office and IT and they have replaced his phone with a shiny new model at least three times.

You can see where this is going....  

(( to be contined ...))

Oh and let me add, as FFNT [fumble fingered non tech] as I am, I am the onsite tech support for my company because I am the most comfortable with computers etc.  So, we're not a bank but a CUSO, so what should I name the tales generated by a small business?

No word on the Libre2 reader yet.


Permalink | Thursday, January 26, 2023