General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: David Collier-Brown <davec-b@rogers.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Motivating commercial entities? tell the sales manager (was: ping loss "considered harmful")
Date: Tue, 03 Mar 2015 14:46:03 -0500	[thread overview]
Message-ID: <54F60F7B.4040405@rogers.com> (raw)
In-Reply-To: <mailman.154220.1425403251.1815.bloat@lists.bufferbloat.net>

[-- Attachment #1: Type: text/plain, Size: 2053 bytes --]

On Mon, Mar 2, 2015 at 12:48 PM, Bill Ver Steeg (versteb) 
<versteb@cisco.com wrote:
> There are several efforts underway within this particular big vendor to
> address bloat. Are these efforts crash programs to get code out the door as
> fast as humanly possible? No. There are efforts underway, though. These
> things take time?? To be frank, the best way to drive feature
> development/deployment/adoption in most big companies is to have customers
> ask for them.

Dave Taht <dave.taht@gmail.com> replied
> Creating understanding and demand has been my nearly f/t project for
> several years now. I hope it is finally starting to work!
>
> However, along the way - in trying to work with everybody in all parts of
> the industry, and to "get along" - I found myself in a deep moral and
> mental hole where I realized I was no longer being true to myself or being
> effective in what I had really set out to do by attempting to create this
> open, shared project, where I had hoped we all would be working together
> for a common goal.

Just a rather specific pointer: it's neither the technical staff nor the 
support team that has the power to report and escalate a bug. /It's the 
sales team/.  If you can elevator-pitch the head of sales for Honeywell* 
with something that will avoid costing him sales, you'll get an informed 
and motivated response from the business.

If you talk to anyone else, they'll need permission from their director 
to even report a bug, and an explicit blessing from a VP to escalate it.

The same is true of most large companies, even if they're not very old.  
If they're market-driven, it the sales and marketing folks who report 
what the market wants.  Techies and CSRs will only be asked /after/ the 
"market" speaks.

--dave
[* Honeywell no longer makes computers, so I can use them as a bad 
example (;-)]

-- 
David Collier-Brown,         | Always do right. This will gratify
System Programmer and Author | some people and astonish the rest
davecb@spamcop.net           |                      -- Mark Twain


[-- Attachment #2: Type: text/html, Size: 2919 bytes --]

       reply	other threads:[~2015-03-03 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.154220.1425403251.1815.bloat@lists.bufferbloat.net>
2015-03-03 19:46 ` David Collier-Brown [this message]
2015-03-03 20:19   ` Dave Taht
2015-03-03 21:08     ` Dave Taht
2015-03-03 21:20       ` Jonathan Morton
2015-03-05 12:46         ` [Bloat] [Bulk] Re: Motivating commercial entities? tell the sales manager David Collier-Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54F60F7B.4040405@rogers.com \
    --to=davec-b@rogers.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=davecb@spamcop.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox