Tuesday, December 8, 2015

Mastering Strategy

The careers of superstar CEOs Bill Gates, Andy Grove, and Steve Jobs offer important lessons about how to become a better strategist.
Many discussions of strategy revolve around companies. But what about the people who develop corporate strategies? How can executives develop their skills as strategists?
There’s no better way than to learn from the masters. That’s the idea behind a recent book by David B. Yoffie, the Max and Doris Starr Professor of International Business Administration at Harvard Business School, and Michael A. Cusumano, the Sloan Management Review Distinguished Professor of Management at the MIT Sloan School of Management. Both men are experts in business strategy — they’ve been teaching the subject for nearly 30 years at Harvard and MIT, respectively. What’s more, Yoffie and Cusumano have studied or worked closely with some of the world’s leading technology executives. In their book, Strategy Rules: Five Timeless Lessons From Bill Gates, Andy Grove, and Steve Jobs (HarperCollins, 2015), Yoffie and Cusumano explore strategy insights drawn from the careers of the former CEOs of Microsoft Corp., Intel Corp., and Apple Inc.
MIT Sloan Management Review editorial director Martha E. Mangelsdorf spoke with Yoffie and Cusumano about what executives can learn from Gates, Grove, and Jobs about mastering the art of strategy. What follows is an edited and condensed version of that conversation.
MIT Sloan Management Review: Your book “Strategy Rules” looks at strategy lessons from three iconic CEOs from the computer industry: Bill Gates, Andy Grove, and Steve Jobs. What made you choose those three CEOs to write about?
Yoffie: There are several reasons for choosing these three. First and foremost, all three of the companies they led — Microsoft, Intel, and Apple — became the most valuable company in the world at some point. We were looking at three companies where we believed it was undisputed that the three individual CEOs had accomplished an extraordinary amount over their careers.
Second, we had spent a lot of time working with or observing all three of these individuals. We knew them, their records, and their companies extremely well. And by identifying three executives whose legacy as CEO was complete — and where the companies they led had continued to perform well after their departure — we could capture a more complete picture. We also understood the problems and occasional failures of these three CEOs, not just their successes.
That was an interesting aspect of the book. It was fun to learn about not just the things that we know about these three CEOs’ successes, but also about some of the things that didn’t go as well and the areas where they changed and developed as executives.
One of the ideas that I found intriguing in your book was your observation that strategic thinking is a capability that leaders develop over time — and that these executives, whom we know as having made some great decisions, didn’t necessarily start off as such accomplished strategists. Say a little bit about that.
Yoffie: Andy Grove is probably the easiest one to talk about, because he started as a scientist in the lab doing R&D. When he took the next step in his career to help launch and build Intel, he was a true operating manager. He was running a division and then became chief operating officer. Grove’s 1983 book, High Output Management, was all about making middle managers more effective; Grove didn’t become an effective strategist until several years into being CEO. Part of what enabled Grove’s development and transformation was his desire to learn new things — to continually go beyond his current capabilities.
For example, Andy was an engineer who initially knew less than nothing about brands. He was selling an industrial product — semiconductors for computers and other electronic devices — to other industrial companies, and the concept of building a consumer brand was far beyond his experience. But he made a large personal effort to educate himself to understand what a consumer brand was and how consumer pull could work for an industrial products company like Intel.
That whole learning process helped lead to the “Intel Inside” marketing campaign in 1991, which made Intel into one of the most valuable brands in the world.
Cusumano: To continue on this question of developing as a strategist, we believe that Bill Gates was a natural strategist and was born to be a strategic thinker. But again, he, too, learned: He learned to expand his horizons. The famous anecdote about Gates is that when IBM first came to him in 1980 for an operating system for IBM’s new personal computer, he sent them off to another company run by Gary Kildall. But when IBM came back to Gates, he clearly understood the opportunity that was ahead — to create the foundation for a whole new industry. Over the years, we’ve seen many examples of brilliant strategic moves by Gates: breaking with IBM; putting his resources behind Windows; embracing and extending the Internet; and then rebuilding Windows and Microsoft Office around the Internet.
What Gates really learned about is execution and organization. He learned that he couldn’t personally run whole areas of the company. He understood coding and algorithms, which allowed him to go one-on-one with engineers, but he went outside the company to hire talented managers with different backgrounds and experiences to run operations and various product groups.
Steve Jobs, on the other hand, always had great product instincts, but he had to learn to master strategy in the high-tech world. The strategy of Apple initially was great products, one product at a time. He only gradually adapted, with pressure from his management team in the 2000s. After resisting for years, Jobs eventually agreed to adopt a broader platform strategy, with a vision of a digital hub that targeted Windows as well as Macintosh users. By the time iPods and iTunes starting rolling out to the broader market beyond Macintosh users, we think Jobs had become a brilliant strategist.
Yoffie: I would also add that Steve was not pragmatic in his first 10 years as Apple’s CEO and that part of what made him a much better strategist by the late 1990s was he became a pragmatist. He recognized that you have to make deals with the enemy — in Apple’s case, Microsoft — and you have to delegate.
In your book, you identify five important strategy lessons that you drew from these three executives’ careers. Can you explain a little bit about the five strategy rules you identified? Let’s go through all five.

Strategy Rule #1: Look Forward, Reason Back

Yoffie: For managers, it’s a natural instinct to look backward and then reason forward about what they need to do today. That involves learning from history, thinking about the problems the business had yesterday, and how to solve similar problems tomorrow. But great strategists are like great chess players or great game theorists: They need to think several steps ahead towards the end of the game and then reason back to what that means about what they need to do today.
As a strategist, you need to think about where you want your business to be two, three, five, seven years down the road and then figure out what are the priorities and boundaries of what you need to do as a company today to get there. You need to be able to anticipate customer needs — not just solving the customer problems of today, but what the customer is going to need tomorrow. Then match that to the capabilities you can deliver in terms of new products and new processes for the customer over the next several years. You also need to anticipate what competitors will do and try to find ways to systematically build barriers to imitation and barriers to entry to reduce the likelihood that competitors will take away your advantage down the road. Finally, you have to be able to think about how whole industries may change.
The core story is a discipline of thinking several steps ahead and then figuring out what that means for the company now. This was a discipline that we saw across all three CEOs.
Cusumano: For example, all three of the CEOs extrapolated from Moore’s Law [the number of transistors on an integrated circuit doubling approximately every 18-24 months] in a different way. In the 1970s, both Gates and Jobs extrapolated that computing power was becoming ubiquitous and cheap, which would give birth to personal computers.
Gates, with Paul Allen in 1975, saw Moore’s Law and reasoned: Computers are just boxes without software. Software could be the source of value. Hardware is going to become a commodity. We’re going to control the software. And Microsoft was essentially the first software product company.
Jobs saw the same thing and concluded: Computers are going to be everywhere. We’re going to make them as easy to use as a typewriter or a toaster, out of the box. We’re going to make the computer a consumer appliance.
It took Grove a little while longer, but after a few years he figured out that Moore’s Law would lead to massive economies of scale and specialization in the computing industry, and that would probably make it difficult for the vertically integrated companies like IBM and Digital Equipment Corp. to maintain excellence and superiority in all the different segments. Grove reasoned that the computing industry would de-integrate into horizontal layers: Microsoft and some other companies would probably dominate software, but Intel would focus on the microprocessor. Eventually, he exited most other businesses, such as commodity memory products, and decided Intel was not going to build full computers and compete with its partners. Intel was just going to focus on that one layer: microprocessors.

Strategy Rule #2: Make Big Bets, Without Betting the Company

Cusumano: All three executives made big bets, but they never really bet the company. They always hedged those big bets. For example, one of Microsoft’s big bets was the decision to break with IBM in 1991. By the time Gates made that decision, Microsoft had many other companies as customers for DOS and then Windows — the PC clone industry. In addition, Microsoft had a small applications business that was growing quite fast. They also had the application business for the Macintosh. Breaking with IBM was a huge gamble, because Big Blue had really made Microsoft into a powerhouse, but Microsoft would not be killed by the divorce.

Strategy Rule #3: Build Platforms and Ecosystems — Not Just Products

Cusumano: These three executives set the intellectual foundations for understanding platform strategy and how it differs from product strategy. I can’t think of any three CEOs who have clarified our thinking more on that enormously important strategic concept.
For example, Gates understood the importance of platforms pretty much immediately in 1980, with Microsoft’s contract with IBM for the DOS operating system. Gates understood platforms through the lens of IBM; he knew IBM’s history quite well. The IBM mainframe had become an industry platform, where other companies had built compatible hardware. There were actual clones of the IBM mainframe. There were many peripherals that were clones, and there was a lot of software that was written to work on IBM and IBM-compatible machines.
Gates states very clearly — and we have the quote in the book — that he knew from day one, when Microsoft structured its deal with IBM to allow Microsoft to license DOS to other companies, that there would probably be a clone industry for personal computers, just like there had been for the IBM mainframe. So he saw that the personal computer would be a platform — and that Microsoft’s operating system could be a key element of that platform.

Strategy Rule #4: Exploit Leverage and Power — Play Judo and Sumo

Yoffie: If you’re going to be a great strategist, you’ve got to be able to execute at the tactical level. The things that you do every day, day-to-day with your customers, with your competitors, and with your partners become critical in your ability to execute your longer-term strategy. You have to be both clever and tough at the same time. The cleverness is the judo idea — trying to find ways to take advantage of your competitors’ strengths and turn them to your advantage, to find ways to avoid head-to-head struggles with your competitors at times when you’re not necessarily strong enough to compete that way.
Here’s an example of a judo tactic in strategy: When Jobs was launching iTunes, Apple only had around 2% of the PC market. So he used that to his advantage in negotiating with music executives; he persuaded them to license music on Apple’s terms as an experiment. In effect, he said: I’m only 2% of the market; what have you got to lose? In that case, being underestimated helped Steve Jobs get his way. That was, in retrospect, a huge mistake by the music industry.
Conversely, when you’re big enough and powerful enough, you have to be tough enough to extract as much value as possible in your interactions with other businesses. That’s the sumo aspect of strategy — not being afraid to throw your weight around. Gates, for example, regularly played hardball with customers and competitors alike. When he wanted Apple to adopt Internet Explorer in his efforts to win the browser wars, he threatened Gil Amelio, Apple’s then-CEO, with shutting down Microsoft Office for the Macintosh. Insiders believed this move could have put Apple out of business. Jobs was no less ruthless; for instance, he bullied book publishers into accepting Apple’s terms to launch the Apple iBookstore with the iPad. But as these two examples suggest, playing sumo means walking a fine line with antitrust. Both Microsoft and Apple faced antitrust battles with the U.S. Department of Justice.

Strategy Rule #5: Shape the Organization Around Your Personal Anchor

Cusumano: This was the hardest rule to describe. We try to explain why these three CEOs were effective at execution. Our answer was that each had a stake in the ground — a personal anchor — that helped them grow their companies, focus strategy, and hire people around.
For Gates, it was his understanding of software, which was as good as anybody in the world at the time he was launching Microsoft, at least for personal computers. For Jobs, it was his uncanny ability to understand the average user, especially the user interface. And Andy Grove had this incredible engineering-like process discipline; it was very clear that what he tried to do was bring the discipline of engineering to the messy business that semiconductor manufacturing was at that time. It was a business that was more art, or trial and error, than science and in which Intel was getting beaten up by the Japanese, who at that time were better at process. But Andy brought this incredibly disciplined and data-driven decision making, and intensity of debate and process discipline, to everything he did — to manufacturing, marketing, and sales, as well as to strategic planning.
Yoffie: Another aspect of a personal anchor is a bit paradoxical: You want to dive deep into the things you’re really good at, but at the same time stay at a high level and always keep the big picture in mind. You have to know yourself, know what you are good at, and know your weak spots. It doesn’t matter whether you’re an entrepreneur or running a $50 billion company; the key thing is figuring out how to compensate for your weaknesses in order to make the organization execute effectively. We think that’s true regardless of company size; any CEO has to do that. In the case of Grove and Gates, they knew very early on in their careers what they were good at and what they weren’t; their crisp execution depended on finding ways to get the right people around them to compensate for areas that weren’t their personal strengths.
In the case of Jobs, of course, he did not appreciate this ‘rule’ in the early days. One of the things he figured out when he came back to Apple the second time, in 1997, was that he really wasn’t good at many things, and he needed a lot of people to help him. He needed to figure out how to do what he did really well and drive that aspect of the organization — and then make sure he had other talented executives to lead areas such as supply chain and finance.
All three executives developed their skills as strategists over the years and became very strong in different ways by the end of their careers.
But as you point out in your book, none of these CEOs’ visions will last forever — particularly not in the fast-changing technology sector. How do these lessons apply to the next generation of technology CEOs? What’s different for the up-and-coming generation of technology entrepreneurs?
Cusumano: We think all of these principles and the details behind them — not just the high-level rules — are of extraordinary use to the next generation. I was recently at a lecture where I saw a list of the most valuable pre-IPO companies, and they’re nearly all platform companies. They’re taking advantage of exponential growth possible over the Internet in some shape or form, whether it’s Airbnb or Uber or many others.
And all of those businesses evolve from looking forward, reasoning back, figuring out what to do; making some big bets; building platforms rather than standalone products or services; figuring out how to be both clever and powerful; and building companies around the strengths of the founders. Most of these companies have a very distinct “edge” — a strategic and technical focus — to them that comes from the founders or the founders’ teams. But if entrepreneurs don’t then build broader teams with more diverse skills, they limit their success and growth.
I think all five principles are valuable for managers. But we also identified two additional lessons that apply to the next generation of entrepreneurs: First, while it is critical to build a company around your personal anchor and make that into an organizational anchor to sustain your advantage, you also have to beware that an anchor can limit you and hold the company back. And second, be aware of an inherent challenge associated with building a successful platform: You become so successful that you see the world through the lens of your platform. Then it gets very difficult to move to whatever comes next.

A Non-Geek’s Big Data Playbook

Introduction ...................................................................................... 4 terms & diagrams used in this playbook................................. 5 The Enterprise Data Warehouse.............................................................. 5 Big Data and Hadoop ............................................................................. 6
 play 1: stage structured data..................................................... 8
 play 2: process structured data ............................................. 10
 play 3: process non-integrated & unstructured data.... 11
 play 4: archive all data................................................................. 13
play 5: access all data via the EDW.......................................... 14
 play 6: access all data via Hadoop........................................... 16 conclusion........................................................................................ 18


Wednesday, October 7, 2015

6 tips for managing highly intelligent employees


Rubiks
IMAGE: FLICKR, THEILR
Don't manage: Guide. IQ and experience are two attributes you want your team members to over-index on, but there are plenty of other attributes that also matter, including judgment, work ethic, communication skills and teamwork. Unlike raw IQ, these are things that can be developed in any employee. Your job is to provide individualized guidance to each of your team members in the areas that they need to develop.
Here are some other general tips for guiding strong engineers.
  • Guide what they build, not how they build. As a manager, your job is to make sure your engineering team is working on the most important things. Your idea of what is most important will often differ from theirs, so you need to spend some time explaining why you feel your priorities are the right ones and letting them make the case for theirs. Once you've agreed on the priorities and outcomes you need, give them latitude to decide how they will achieve them.
  • Ask probing questions. Ask them what their design optimizes for, what their availability target is, what the latency requirements are, why they chose a particular persistence layer, why they chose the specific language, etc. Ask them what the standard in your company is for X or Y, and why they chose to diverge from the standard. Doing so will not only educate you, but also give you an opportunity to spot potential inconsistencies in their design or fuzzy thinking in general.
  • Connect them with very senior engineers even smarter or more experienced than they are, and set up a process to leverage that experience. This supports your engineers' learning and development and also ensures that their designs get an adequate architectural review if you're not equipped to perform one yourself.
  • Mediate arguments and (too) long-running discussions. Strong engineers have confidence in their design and coding judgment, and are inclined to get into debates with other engineers about the right way to do things. This is productive, to a point, but eventually it starts becoming unproductive and can create tension.
    Your job as a manager is to find ways to short-circuit arguments and long-running debates,
    Your job as a manager is to find ways to short-circuit arguments and long-running debates, which may mean listening to diverging viewpoints and then making a decision. If you're not equipped to make the decision, find a path to do so, which might mean reviewing with a very senior engineer not on your team and letting him or her make the decision.
  • Continue to hire team members smarter than you. You may want to balance a team of mostly experienced engineers with some more junior engineers, but you always want to hire for high raw technical IQ. Hiring an engineer is a long-term decision. Don't relax your standards in order to fill an engineering role quickly.
  • Manage out poor performers. Strong engineers don't like to work with weak ones. If you don't manage out poor performers, your team will accumulate them and your strong performers will move on to other teams or companies.

Saturday, September 26, 2015

15 Awesome Examples to Manipulate Audio Files Using Sound eXchange (SoX)

This article is part of the on-going Software for Geeks series. SoX stands forSound eXchange. SoX is a cross-platform command line audio utility tool that works on Linux, Windows and MacOS. It is very helpful in the following areas while dealing with audio and music files.

  • Audio File Converter
  • Editing audio files
  • Changing audio attributes
  • Adding audio effects
  • Plus lot of advanced sound manipulation features

In general, audio data is described by following four characteristics:
  1. Rate – The sample rate is in samples per second. For example, 44100/8000
  2. Data size – The precision the data is stored in.  For example, 8/16 bits
  3. Data encoding – What encoding the data type uses. For example, u-law,a-law
  4. Channels – How many channels are contained in the audio data.  For example, Stereo 2 channels
SoX supports over 20 audio file formats. To get the list of all supported formats, execute sox -h from the command line. One of the major benefits of a command-line audio/music tool is easy to use in scripts to perform more complex tasks in batch mode.

All the 15 examples mentioned below can be used to manipulate Audio files on Unix, Windows and MacOS. Make sure to download the corresponding SoX utility for your platform from the SoX – Sound eXchange download page.

1. Combine Multiple Audio Files to Single File

With the -m flag, sox adds two input files together to produce its output. The example below adds first_part.wav and second_part.wav leaving the result in whole_part.wav. You can also use soxmix command for this purpose.
$ sox -m first_part.wav second_part.wav whole_part.wav

(or)

$ soxmix first_part.wav second_part.wav whole_part.wav

2. Extract Part of the Audio File

Trim can trim off unwanted audio from the audio file.
Syntax : sox old.wav new.wav trim [SECOND TO START] [SECONDS DURATION].
  • SECOND TO START – Starting point in the voice file.
  • SECONDS DURATION – Duration of voice file to remove.
The command below will extract first 10 seconds from input.wav and stored it in output.wav
$ sox input.wav output.wav trim 0 10

3. Increase and Decrease Volume Using Option -v

Option -v is used to change (increase or decrease ) the volume.

Increase Volume

$ sox -v 2.0 foo.wav bar.wav

Decrease Volume

If we need to lower the volume on some files, we can lower them by using negative numbers. Lower Negative number will get more soft . In the following example, the 1st command (-0.5) will be louder than the 2nd command (-0.1)
$ sox -v -0.5 srcfile.wav test05.wav

$ sox -v -0.1 srcfile.wav test01.wav

4. Get Audio File Information

The stat option can provide lot of statistical information about a given audio file. The -e flag tells sox not to generate any output other than the statistical information.
$ sox foo.wav -e stat
Samples read: 3528000
Length (seconds): 40.000000
Scaled by: 2147483647.0
Maximum amplitude: 0.999969
Minimum amplitude: -1.000000
Midline amplitude: -0.000015
Mean norm: 0.217511
Mean amplitude: 0.003408
RMS amplitude: 0.283895
Maximum delta: 1.478455
Minimum delta: 0.000000
Mean delta: 0.115616
RMS delta: 0.161088
Rough frequency: 3982
Volume adjustment: 1.000

5. Play an Audio Song

Sox provides the option for playing and recording sound files. This example explains how to play an audio file on Unix, Linux. Playing a sound file is accomplished by copying the file to the device special file /dev/dsp. The following command plays the file music.wav: Option -t specifies the type of the file /dev/dsp.
$ sox music.wav -t ossdsp /dev/dsp
You can also use play command to play the audio file as shown below.
Syntax :play options Filename audio_effects

$ play -r 8000 -w music.wav

6. Play an Audio Song Backwards

Use the ‘reverse’ effect to reverse the sound in a sound file. This will reverse the file and store the result in output.wav
$ sox input.wav output.wav reverse
You can also use play command to hear the song in reverse without modifying the source file as shown below.
$ play test.wav reverse

7. Record a Voice File

‘play’ and ‘rec’ commands are companion commands for sox . /dev/dsp is the digital sampling and digital recording device. Reading the device activates the A/D converter for sound recording and analysis. /dev/dsp file works for both playing and recording sound samples.
$ sox -t ossdsp /dev/dsp test.wav
You can also use rec command for recording voice. If SoX is invoked as ‘rec’ the default sound device is used as an input source.
$ rec -r 8000 -c 1 record_voice.wav

8. Changing the Sampling Rate of a Sound File

To change the sampling rate of a sound file, use option -r followed by the sample rate to use, in Hertz. Use the following example, to change the sampling rate of file ‘old.wav’ to 16000 Hz, and write the output to ‘new.wav’
$ sox old.wav -r 16000 new.wav

9. Changing the Sampling Size of a Sound File

If we increase the sampling size , we will get better quality. Sample Size for audio is most often expressed as 8 bits or 16 bits. 8bit audio is more often used for voice recording.
  • -b Sample data size in bytes
  • -w Sample data size in words
  • -l Sample data size in long words
  • -d Sample data size in double long words
The following example will convert 8-bit audio file to 16-bit audio file.
$ sox -b input.wav -w output.wav

10. Changing the Number of Channels

The following example converts mono audio files to stereo.  Use Option -c to specify the number of channels .
$ sox mono.wav -c 2 stereo.wav
There are methods to convert stereo sound files to mono sound.  i.e to get a single channel from stereo file.

Selecting a Particular Channel

This is done by using the avg effect with an option indicating what channel to use. The options are -l for left, -r for right, -f for front, and -b for back.  Following example will extract the left channel
$ sox stereo.wav -c 1 mono.wav avg -l

Average the Channels

$ sox stereo.wav -c 1 mono.wav avg

11. Audio Converter – Music File Format Conversion

Sox is useful to convert one audio format to another. i.e from one encoding (ALAW, MP3) to another. Sox can recognize the input and desired output formats by parsing the file name extensions . It will take infile.ulaw and creates a GSM encoded file called outfile.gsm. You can also use sox to convert wav to mp3.
$ sox infile.ulaw outfile.gsm
If the file doesn’t have an extension in its name , using ‘-t’ option we can express our intention . Option -t  is used to specify the encoding type .
$ sox -t ulaw infile -t gsm outfile

12. Generate Different Types of Sounds

Using synth effect we can generate a number of standard wave forms and types of noise. Though this effect is used to generate audio, an input file must still be given, ‘-n’ option is used to specify the input file as null file .
$ sox -n synth len type freq
  • len – length of audio to synthesize. Format for specifying lengths in time is hh:mm:ss.frac
  • type is one of sine, square, triangle, sawtooth, trapezium, exp, [white]noise, pinknoise, brown-
    noise. Default is sine
  • freq – frequencies at the beginning/end of synthesis in Hz
The following example produces a 3 second 8000 kHz, audio file containing a sine-wave swept from 300 to 3300 Hz
$ sox -r 8000 -n output.au synth 3 sine 300-3300

13. Speed up the Sound in an Audio File

To speed up or slow down the sound of a file, use speed to modify the pitch and the duration of the file. This raises the speed and reduces the time. The default factor is 1.0 which makes no change to the audio. 2.0 doubles speed, thus time length is cut by a half and pitch is one interval higher.
Syntax: sox input.wav output.wav speed factor

$ sox input.wav output.wav speed 2.0

14. Multiple Changes to Audio File in Single Command

By default, SoX attempts to write audio data using the same data type, sample rate and channel count as per the input data. If the user wants the output file to be of a different format then user has to specify format options. If an output file format doesn’t support the same data type, sample rate, or channel count as the given input file format, then SoX will automatically select the closest values which it supports.
Converting a wav to raw. Following example convert sampling rate , sampling size , channel in single command line .
$ sox -r 8000 -w -c 1 -t wav source -r 16000 -b -c 2 -t raw destination

15. Convert Raw Audio File to MP3 Music File

There is no way to directly convert raw to mp3 file because mp3 will require compression information from raw file . First we need to convert raw to wav. And then convert wav to mp3.  In the exampe below, option -h indicates high quality.
Convert Raw Format to Wav Format:
$ sox -w -c 2 -r 8000 audio1.raw audio1.wav
Conver Wav Format to MP3 Format:
$ lame -h audio1.wav audio1.mp3

Using Sox spectrogram tool to analyze audio noise


While out on a walk near Lagos (Algarve, south Portugal) I noticed a loud buzzing/crackling sound. It sounded very similar to the kind of buzz/crackle you'd hear near high voltage transmission lines, but there was no power lines in sight. So I though I'd capture a few seconds of audio with a voice recorder app on my phone and look at the spectrum later to rule in/out an electrical origin: any thing electrical would have peaks at exactly 50Hz and harmonics of 50Hz.
It turns out that sox has a neat tool to create a spectrogram from any audio file:

sox recording.wav -n spectrogram -o spectrum.png

However the frequencies I was interested in were down well under 1kHz, so I first resampled at a rate twice the highest frequency of interest:

sox recording.wav -r 2k -o t.wav
sox t.wav -n spectrogram -o spectrum.png

So this is the result:



The buzz sound can be seen in the spectrograph as horizontal streaks at about 60Hz and 120Hz. Not being exactly 50Hz rules out an electrical origin. The frequency can also be seen to vary a little with time.

Here is a spectrogram of another recording I took on the way down to the beach later. There was multiple sources in this recording (audio file here) but fainter/further away.



and other (audio file here):


You can see multiple horizontal streaks  of varying frequencies.

Conclusion:

It's clear now the noise is from an insect. What insect, I have no idea. (Update: I think it might be Cicada)

If puzzled about the origin of a strange sound, record it and create a spectrogram... it might yield clues. Anything relating to utility power will be at the AC frequency (50Hz most of the world, 60H

Sunday, September 20, 2015

Breaking the model of Customer Care

Customer Care is facing a dilemma.

The market has changed but the discipline hasn’t. Customers want better service, they want it in every channel, and they want it now.
But better service costs more. It’s always been that way.
Until now. Finally, new technologies are breaking the link between low cost and low levels of service. And they’re transforming the dynamics of Customer Care forever, delivering lower costs and higher levels of service.
This slideshare will show you just how that’s possible. We hope you enjoy it.

Contact Us: Call 1-877-414-2676 

Tuesday, September 15, 2015

Why Curious People Are Destined for the C-Suite


SEPTEMBER 11, 2015

RECOMMENDED

SEPT15_11_160019812
When asked recently to name the one attribute CEOs will need most to succeed in the turbulent times ahead, Michael Dell, the chief executive of Dell, Inc., replied, “I would place my bet on curiosity.”
Dell was responding to a 2015 PwC survey of more than a thousand CEOs, a number of whom cited “curiosity” and “open-mindedness” as leadership traits that are becoming increasingly critical in challenging times. Another of the respondents, McCormick & Company CEO Alan D. Wilson, noted that business leaders who “are always expanding their perspective and what they know—and have that natural curiosity—are the people that are going to be successful.”
Welcome to the era of the curious leader, where success may be less about having all the answers and more about wondering and questioning. As Dell noted, curiosity can inspire leaders to continually seek out the fresh ideas and approaches needed to keep pace with change and stay ahead of competitors.
A curious, inquisitive leader also can set an example that inspires creative thinking throughout the company, according to Hollywood producer Brian Grazer. “If you’re the boss, and you manage by asking questions, you’re laying the foundation for the culture of your company or your group,” Grazer writes in his book, A Curious Mind. Grazer and others maintain that leading-by-curiosity can help generate more ideas from all areas of an organization, while also helping to raise employee engagement levels.
The notion that curiosity can be good for business is not entirely new, of course. Decades ago, Walt Disney declared that his company managed to keep innovating “because we’re curious, and curiosity keeps leading us down new paths.” But having that desire to keep exploring “new paths” becomes even more important in today’s fast-changing, innovation-driven marketplace.
In my own research for my book, A More Beautiful Question, I found numerous examples of current-day entrepreneurs and innovators—including Netflix’s Reed Hastings, Square’s Jack Dorsey, and the team behind Airbnb—who relied on curious inquiry as a starting point to reinventing entire industries. Dorsey, for example, was puzzled when an artist friend lost a big sale to a potential customer simply because the artist couldn’t accept a credit card. Dorsey wondered why only established businesses, and not smaller entrepreneurs, were able to conduct credit card transactions; his search for an answer resulted in Square, a more accessible credit card reader.
While curiosity has ignited numerous startup ventures, it also plays an important role at more established companies, where leaders are having to contend with disruptive change in the marketplace. “These days, a leader’s primary occupation must be to discover the future,” Panera Bread CEO Ron Shaich told me. It’s “a continual search,” Shaich says, requiring that today’s leader keep exploring new ideas—including ideas from other industries or even from outside the business world.
Advising business leaders to “be more curious” sounds simple enough, but it may require a change in leadership style. In many cases, managers and top executives have risen through the ranks by providing fixes and solutions, not by asking questions. And once they’ve attained a position of leadership, they may feel the need to project confident expertise.
To acknowledge uncertainty by wondering aloud and asking deep questions carries a risk: the leader may be perceived as lacking knowledge. In their book The Innovator’s DNA, authors Clayton Christensen, Hal Gregersen and Jeff Dyer observed that the curious, questioning leaders they studied seemed to overcome this risk because they had a rare blend of humility and confidence: They were humble enough to acknowledge to themselves that they didn’t have all the answers, and confident enough to be able to admit that in front of everyone else.
While we may tend to think of curiosity as a hardwired personality trait—meaning, one either is blessed with “a curious mind” or not—according to Ian Leslie, author of the book Curious, curiosity is actually “more of a state than a trait.” We all have the potential to be curious, given the right conditions.
Leslie notes that curiosity seems to bubble up when we are exposed to new information and then find ourselves wanting to know more. Hence, the would-be curious leader should endeavor to get “out of the bubble” when possible; to seek out new influences, ideas, and experiences that may fire up the desire to learn more and dig deeper.
Even when operating within familiar confines, curious leaders tend to try to see things from a fresh perspective. The ones I studied in my research seemed to have a penchant for bringing a “beginner’s mind” approach to old problems and stubborn challenges. They continually examined and re-examined their own assumptions and practices, asking deep, penetrating “Why” questions, as well as speculative “What if” and “How” questions.
Such leaders sometimes also evangelize about curiosity, urging people in their organizations to “Question Everything.” This can serve to model the behavior for others, though leaders may have to go much further—providing sufficient freedom and incentives—in order to actually create the conditions for curiosity to flourish company-wide.
In the end, it isn’t necessarily easy for a leader to foster curiosity on an individual or organizational level—but it may be well worth the effort. “With curiosity comes learning and new ideas,” says Dell. “If you’re not doing that, you’re going to have a real problem.”