Showing posts with label Spark. Show all posts
Showing posts with label Spark. Show all posts

Tuesday, November 7, 2017

Meetings sucked but they don't have to anymore!

Today I attended a seminar about the modern meeting. Thank you to Logitech who sponsored the seminar, and also to Microsoft and Pexip who presented, and finally to the guest speaker, Dave Michels, who gave an excellent talk which i will borrow from and expand upon below. These are my words and ideas, but Dave reinforced them and made me want to write a little about them here.

Let's reflect on a simple truth - meetings suck.

They are an anachronism from a time of TPS reports and heavily regimented hierarchical structures incompatible with the modern American organization.

Do you come out of a weekly 60 minute status/team meeting and feel 120 minutes older?
     I know I do...

Meetings must die.
     Long live the meeting!

Just to get started, here are my recommendations for meetings:

  • Never host or goto a meeting without a clear agenda or purpose
    • Include the agenda in the meeting invitation and relevant documents with the meeting (or even better - links to them)
  • Never schedule a meeting for something that can be handled in email or IM
    • Remember that status reports and project updates should be a part of a project management system and not a meeting
  • Schedule meetings for WAY less than an hour - think 15, 30 but never more than 45 minutes
    • Ask yourself, "do we NEED this meeting/time?" - remember this is probably time that everyone can be more productive doing their jobs
    • Ending early isn't "giving you back your time," it's just a good idea
  • If you don't need to be there, then you shouldn't have the meeting
  • Meeting time isn't social or complaint time so a leader should direct the conversation so the agenda/purpose of the meeting can be completed efficiently and quickly (wrap business up before the social sessions)
These simple things are a first step in making meetings better.  Notice that they also discourage meetings. I intend to preach this idea far and wide because "meetings" are evolving; the act of consciously devoting cycles to stopping work and talking about your work has been componentized and redistributed in function by a number of different tools. Decades of thought have gone into this but the changes have come very quickly and are remain is a huge state of flux as the competitive markets see who wins.

What is changing these meetings? 
In the IT world a dozen or so years of Project Management, ITIL, and many other methodologies have standardized business practices. When we all work the same way, or at least have an understanding of how we should work towards a goal, we don't need to meet as often to figure out how we will wing our way through the next week. Standardization helps!    With this, we have many tools to track projects, assign tasks, and fiddle with all kinda of levers that traditionally we had meetings for. Just look at email - it killed the memo and has been leveraged to avoid meetings for forty years now! Many other areas have seen similar standardization and tools come into regular usage and we can always use them to reduce wasted meeting time.

Video and voice conferencing has become pervasive in the workplace and in our everyday lives. We've tied these into our phone systems and added messaging and made them all work from everywhere. This rapidly changing technology is nearly commoditized such that everyone everywhere can communicate as if they were in an old-fashioned meeting but in a short ad-hoc impromptu way. This can avoid the interruptive nature of a scheduled meeting yet still allow the face to face productive benefits than single model communications cannot.
Think about communications in the different models we might use: written < verbal < documents < visual. Each model provides more information and therefore more context than the previous but also requires more attention. Retention also increases with each as well.
The coming revolution might lie in what Dave referred to as "Work Stream Apps." I like that name as it appropriately describes what Slack, Cisco Spark, Microsoft Teams and similar can do. Think  about those models I just described; each was completely separate not long ago. Talking to someone on a phone required a very separate set of infrastructure than sending them a document but how often did you have to do both at the same time? A work stream app allows you to multitask your communication (or meeting) such that textual messages exist in the same space as the documents they reference and those involved can start a voice call about the topic instantly without leaving the same app, or even add in video participants. 

When we consider Work Stream Applications, the traditional meeting does not need to exist. We have distilled it down into a concentrate that fits better into the way we work. When a team or functional group is working on something from diversa locations and times, they can keep each other up to date without ever having interrupted their work. This isn't even an EOD handover - it's an active ongoing conversation (ok, a never ending meeting). When there is a situation that the keyboard/finger combo turns to head/desk, you can push a button to start using your words OR gesticulate a little. 

As I said, these ideas are in flux right now as the pioneers see the big guns crowding the market with their different take. Everything will change in the next few years. It is possible that "work stream apps" become too monolithic and are rejected by users. It is hard to tell for certain, but having seen how componentized these things are I am confident in saying that if you are in Collaboration, Telecommunications, Unified Communications or Messaging and you are not paying attention then you are behind the ball.


Meetings? Are ya with me?

Monday, October 23, 2017

The power of Social Media and Collaboration

I was asked last week about "social media" and work and I have been thinking about it a lot since then.

Twitter, blogging, chat groups and community message boards are definitely a very powerful tool, even more so in some of the more specialized fields like collaboration, voice, telepresence and UC. I am active in attending what user groups I can, but the online social communities really give me the feeling that I am not alone in this technology.

Some of the first user groups I ever attended were the Seattle chapter of the Avaya Users Group - it's one of the largest in the country so I was lucky to experience it. There is the natural chance to commiserate with people who handle the same stuff everyday, and the opportunity to learn form their experiences. But organizing these groups is difficult and takes a different type of leadership.

I make sure to attend the Skype Users Groups here - they are usually hosted by Microsoft and run by members and sponsored by companies and vendors with a keen interest in informing and engaging with their customers. I always learn good things - a few weeks ago we had a dive into Microsoft Teams (I came away impressed).

Social Media - that is Twitter, blogs, online communities, ongoing chats and the like - really fills that gap. It keeps me from feeling like I am the only one in the world working on this stuff. I get ideas from other, keep up to date with news, but more importantly I can put out my thoughts so they organize more easily. I'm not obsessive about my social activities and I probably overshare. If I occasionally sound like an idiot then hopefully someone calls me on it.  But really it has helped me grow and so I love it.

Please share your opinions and experiences! Has being social helped you? Where do you keep social?

Tuesday, August 15, 2017

Did I forget about the lab??

Golly no! I just haven't written much lately what with life and all and things work related. But my free Office365 licenses are running up soon so I better migrate to a less Microsoft world.

First and Last thoughts on O365

Look, Microsoft is the defacto standard for many reasons and there is little to fault with this stuff. Microsoft certainly did have it's 70's Detroit era products (Vista and Millennium for example), but brought it back strongly with XP and the associated Office suite. Their back office and server products took off about then and continued to accelerate. 

Take all rough to manage server voodoo, plop it up into the cloud then give it an attractive price - you've got something magic that should be hard for any small or medium business to resist. Seriously, At $20/month per head you get something whole IT orgs normally maintain. 

OK, I am not going to get any money trying to sell this so I'll move onto what i know more. and that's Skype4B and the collaboration tools provided. The hardest part about my trial and Skype is not in the configuration. It wasn't in the testing. No, everything went so incredibly easy! 

Without going into the not-gory detail review, after signing up, I had to insert a string into my DNS records for nosaturn.com to prove it's my domain and then follow the instructions to update the SRV records for Skype federation. I also had to setup some email redirection but again, everything was simple and I was up and running in a couple hours at most. Read Starting a business (or setting up an IT Department)  where I cover it more but that was about the size of it.

Back to the hardest part - why shouldn't everyone use Skype4B then? If you don't laugh after reading that then just do it and be very happy with great and easy to manage complete authentication, email, messaging, internal webpage, file sharing, and so much more IT organization that Microsoft is selling for a pretty amazing price. For a few extra bucks they will even let you call regular old phone numbers and accept incoming phone calls.

Office365 and Skype for Business are a bad choice

With that extreme statement I plant the flag down and boldly declare something that is actually pretty true. You see for every reason this O365 business is wonderful, the actual use might have different needs or objectives in mind. While O365 is amazingly flexible, it simply isn't everything everyone always needs. Every IT org and the software they use varies a little and so do their needs whether it is legacy choices or whatever. 

I could dive deep on the Skype4B is cheating with SIP bandwagon or i could leave it at it takes work for Skype4B to talk to things that are not Skype4B. There is good about that but having a background in voice and networking makes me see Skype4B as an interesting product but not a real telecommunications system. 

While VoIP and WebRTC are very different from their analog and TDM forbearers, you can get down in them and see their evolution. Skype4B grew out of a media streaming toy tossed into Windows 95 back in the days of dial up modems. Use a tidy little codec to slice up your noises and another to pixelate your good looks then sling across the information articles and boom! NetMeeting! It diverged some to and fro within Microsoft picking up new features and names along the way, but also changing the core bit that made it work (those little codecs). What we have ended up with is something that outwardly works and acts like a phone and a video conference application but doesn't use any of the fundamental "systems" that make those work for every other system sold. So you end up adding more and more bits and bling to make it work.......
/rant

What are your alternatives?

If you are small and need to stay in the cloud because you can't handle even the smallest data center your choices are quite abundant. Vonage, ShoreTel, and so many others offer out of the box solutions or you can roll your own quite easily in your pillowy AWS space with a little Asterisk punctuation*     (*must love Linux).    Ward Mundy's blog NerdVittles  has even better info for the roll your own crowd. 

Eventually an organization has to grow up and look at something grown ups choose from big industry players like Avaya and Cisco, right? Rght?      NO!     You be a tiny fish in the big pond of standards=based telecommunications and collaboration tools! 

Spark this fire, get things burning!

Cisco offers a cloud based communications and collaboration package that is flexible in sizing and powerful in it's reach. The basic package lets you make SIP standards-based calls and have persistent chat communications with anyone in the world for free. (for companies of one). Their option levels and pricing are reasonable for larger companies and that's when you get the more important administrator tools. When you fully option a user out, they will be able to host meetings in Spark or even in WebEx, can join from a PC or phone or tablet or regular phone as a voice call or get a desk phone that works directly on it or from any of Cisco's modern TelePresence endpoints or from any other standards-based endpoint and even from Skype. That's like 9 ways to connect without counting variants of each (Windows vs MacOS vs a web browser on Linux). 

Again, I shouldn't try to be selling these things. But I will be fair and remind you I am a Cisco Champion for Collaboration so I am a little biased to Cisco products. But I like Spark and Ive been using it for months now

Its late Brian.... wrap this up.

I opened this window and started typing about how I was moving my perfectly functioning IT department from Skype4B to Cisco Spark. 1000 words later and I haven't moved a thing. Let's see how this goes because I finally got my Spark trial pack :)

Whatcha doing tomorrow?
What are your thoughts?






Sunday, July 9, 2017

Blogging, Tweeting, Linked Inning, Sparking and IFTTTing

Confession; I have never blogged before. 

Since joining Twitter 10 years ago I have tweeted 16.2k times. Twitter has always been more my style because brevity befits my balderdash (ooh i like that). Extending my posts may not be as much a problem as learning the practical mechanics of starting and maintaining something like this.

So this is how I'm proceeding:
  1. Bought the NOSaturn.com domain via Domains.Google.com 
  2. Tried to connect my new domain to a new Blogger blog, but had to figure out first how to delete some blog I made a dozen years ago about nothing (I only posted twice) (that doesn't really count as blogging does it?)
  3.  OK, really setting up the Blogger blog and choose the URL http://blog.NOSaturn.com because I might someday want a real front page
  4. Set Blogger to redirect http://NOSaturn.com to the blog because I don't have that real landing page 
  5. Much Much playing and experimenting with Blogger and layouts and formats and discovering what holes I have in the configurations
That was a whole lot of fun and I see some neat features about the domain tools offered. The SRV tools could allow me to connect potential future lab to real world communication abilities. 😎  But I have to admit a real annoyance that Blogger does not allow HTTPS: redirects with custom domains. regular HTTP needs to die.

Now that I have a blog with a a couple of entries, I ought to connect it to some of the socials I use. I'm not going to connect to Facebook since that's entirely a personal social thing whereas I mix personal and professional in Twitter. You'll find me on LinkedIn too because I hear that I should be there.

My professional presence on social media is encouraged as I am a 2017 Cisco Champion for Collaboration. I'll talk about that another time.

Ah, yes; back to connecting this blog to social media.... IFTTT, or IF This Then That, is a super useful and pretty easy way to make a "trigger" in one thing do "something". In this case I setup an applet that would post to Twitter and LinkedIn whenever I made a blog entry. The post would include the hashtag #Collaboration because that is what hashtags are for. This was real neat right up to the point that I got way too smart and built an applet that would take any of my tweets with #Collab and post that as a blog entry. 
    Don't do that.
Thankfully I stopped all that nonsense because a blog post triggered a tweet which then triggered a blog post of the tweet and on and on. This is like aiming a video camera right at a screen showing the camera's feed. 

I still wanted some of that same functionality but figuring that Blogger should easily be able to tweet or LinkedIn for me I started exploring again. Blogger's Help forums pointed me to some tool that has shut down, then on to DLVR.it which seems to suite me right now. We will see...

Speaking of applets, the new hotness is of course BOTS! There really isn't much difference between applets, apps, bots or all these things except who is using whatever term at any one time. (right?) One of the collaboration tools I'm enjoying lately is Cisco's Spark. It's a mashup of messaging, chat, voice, video, email, file sharing and other general goodness but I will cover that later. Spark has bots and integrations that really enhance and extend it's functionality. I setup a connection in Spark to Twitter so I could Tweet directly from Spark. That worked. Of course if I included the #Collab hashtag the Twitter post then rolled on up into a blog post. NEAT. I cleaned it up even more with another IFTTT applet that would take something I say in a designated Spark room would post directly to my blog. EVEN NEATER.

This is all a very long winded explanation for today's previous posts and a couple I deleted last night from the recursive posting debacle. 
(Remember that "brevity befits my balderdash"? )


This blog really is an extension of my ongoing professional development. There are so many tools and communication modes available now. I really believe understanding their strengths and weaknesses is central to collaboration. 

New Spark message from Brian Haley (Personal)

OK, so that worked... but I am going to disable this for now. Maybe at some point I'll look into a more direct @CiscoSpark to Google Blogger integration. It would also be fun to use some of the Spark Dev tools to bring Spark directly to this page.

from Spark

New Spark message from Brian Haley (Personal)

Let's see if IFTTT will take this Spark Message and post it to my blog

from Spark