Skip to main content

Google Plus could be the first PRM (Personal Relationship Manager)

My toolkit

Last night I was at a great API meetup put together by Shanley (@shanley) from ApiGee.  There were a few interesting presenters including SalesForce.com and Context.IO.  Thinking about CRM, extracting useful content out of e-mail and playing with Google Plus gave me an idea:

One thing that I love in the corporate world that is not yet in my consumer arsenal is a relationship manager.  By that I mean the organized view of: e-mails, phone calls, meetups, personal meetings, group affiliations, shared documents and shared pictures all in one view.

I really don’t need a relationship manager for people I stay in close contact with.  I know exactly what my relationship with my mom is about and I know what’s going on with my close friends.  However there is a distant fringe of people that I come in contact with every once in a while.  It would be great to have a view of our history together.  Under that category I would put: ex co-workers, tax accountants, dentists, doctors, car repair people, some of my college buddies and technical affiliates.

There are only a few companies out there that can actually gather that information and organize it.  I believe Google is in the position to do it well.  In fact creating the PRM would elevate the value of using Google voice, sharing Google docs, joining Google groups and, of course, using Google Plus. 

Comments

jmania said…
Great point! Xobni is a great start for this - sign up for the beta here: http://www.xobni.com/gmailbeta

We also have apps for Outlook and BlackBerry, with iPhone and Android coming later this year.

Basically Xobni will index your mail and, optionally, your phone activity, and will automatically create a profile for every single person you interact with. Those people are ranked so that it's easy to find the right person. When you access that profile, you'll see the last messages you exchanged, and other details about your history with that person, including who you have in common and contact details grabbed from signatures.

Give it a whirl and let me know what you think! I'm at josh @xobni.com. When you sign up for the beta, use the priority code XOBNI-JOSHJ to get in quicker.

Popular posts from this blog

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…

Should this be a microservice?

After having developed several distributed systems and been a part of dozens of architectural discussions I decided to put together a way to frame the microservices debate. Microservices have been fashionable for some time. A lot of it stemmed from the fact that big and successful cloud companies are using microservices.  It seems reasonable that to create a “serious system” one must be using serious tools and architecture, today it’s microservices.  No engineer wants to be called out for creating a solution that “doesn’t scale.”

The definition for a microservice varies, but overall it tends to be a piece of your system that can run somewhat independently (unless of course it depends on other microservices) and has a REST or queue processing interface.  Overall code encapsulation and separation of concerns have all been around for a long period of time.  Current evolution with containers, fast networks and REST API allows people to easily integrate pieces of their system using web se…