Showing posts with label Don&#039t. Show all posts
Showing posts with label Don&#039t. Show all posts

Wednesday, July 25, 2018

It Pays to Know What You Don't Know

Knowledge is power but much depends on how asymmetric it is: what do you know that others don"t and vice versa. Below are four strategically different levels of know-how plus some of the strategies you can use to leverage each to advantage.

The complex issue of handling asymmetric information is central to the field of game theory-- a rigorous analytic discipline used widely in economics, business, strategy, political science, law and more. I"ll address here the mind-twisting problem of how much you know about what others do and don"t know, and conversely, what they know about what you do and don"t know. This may seem esoteric but we encounter such issues daily. Let"s start simple and then build up the layers of asymmetric know-how.

Level 1: Only You Know About a Misdeed. Suppose you find out that your main competitor has stolen some of your intellectual property (IP) or other assets, and is using this against you. It could be some proprietary software, a customer list, a supplier contract, wage scales, your pricing strategies, or other confidential know-how. Often the IP thieves will be within the organization, as happened to the National Security Agency and numerous companies in such fields as oil & gas, agricultural seeds, and all manner of technology. The U.S. Department of Commerce estimated that IP theft has accounted for trillions in lost value. Much of this comes from industrial espionage by outsiders as well, especially China, although many countries and rivals play this game.

Your first reaction when learning that your secrets were stolen may be to cry foul and call the lawyers. But there may be advantage in you knowing something about their misdeeds while they don"t know that you know. First, you could infringe some of their IP as payment in kind, with a soft hint that two can play this game. This may lead to tacit collaboration, a formal licensing arrangement, or conflict resolution less costly than an ugly shoot out at high noon with legal gun slingers. Also, reconciliation can build understanding, trust or even empathy. For example, when parents find out that their young child stole some of their cash, smoked pot or drank alcohol, they can jump all over the kid or gently signal awareness, in ways that allow for face saving self-correction and maturation of the child.

Level 2: The Other Party Knows You Know. Suppose, however, that your competitor finds out on its own-- without you having informed them-- that you know that they have violated your IP. What should you do in this symmetric knowledge situation about the violation? First, it may not be truly symmetric because the rival may not know that you know that they know. This is akin to a child knowing that his parents found out about the smoking or drinking, while still being unsure about whether they know that he knows that. For example, it could be that the maid told the child that the parents know. As before, it may be wise to keep such meta-knowledge (i.e. what each of you know about what the other knows) asymmetric since the situation may automatically correct itself. The child will either stop his misdeed or become even more devious perhaps-- although he now realizes that his parents are not as clueless as he previously assumed.

Level 3: A Child Knows His Parents Know that He Knows. Suppose that the child discovers, perhaps from the maid, that his parents now know that he knows that they have uncovered his nefarious deeds. This would be embarrassing, even though some semblance of ignorance can still be feigned, since his parents have not directly confirmed this by confronting him. Perhaps the maid lied and is playing her own game to get the child to cease his infractions, concerned that the parents will blame her for not telling them. Without complicating this layer cake further, with the maid"s varying degree of knowledge and hidden agendas, it should be clear that knowledge asymmetry can happen at multiple levels.

The first is knowledge about presumed acts of behavior (such as an IP infringement). The second level concerns the parties" awareness about what the other side knows and doesn"t know. The game theory aspects of just the two-party conflict becomes more complex at this higher strategic level. It will seldom be optimal to put all cards on the table if tactical advantage is the aim, since judicious signaling, while avoiding loss of face, may lead to better outcomes. In international negotiations about violations of trade agreements, for example, a piecemeal approach may lead to better outcomes than fully escalating the conflict with hurt egos and further recriminations.

Level 4: Full Parity - Everybody Spills the Beans. Suppose, however, that parents tell their child that they know he knows that they know; the strategic situation now will reach a different level of meta-knowledge yet. If the indirect approach mentioned in level 3 does not work, then in anything from corporate disputes to child rearing to marital infidelity, it may pay to put all cards on the table. If restricted to one single issue, such as a stolen customer list or a child smoking pot, talking it all out may--perhaps with the help of a professional counselor--be cathartic. But when multiple issues are at stake, or if there are more than two aggrieved parties, the situation may call for seasoned negotiators who know when to separate or combine issues. One problem is that you will never know for sure that everyone has shared all they know, although legal clauses with punitive damage levels may get you close.

The general advice in complex cases of conflict is to pursue principled negotiations rather than positional bargaining, as explained in Getting to Yes. Try to agree on the principles that should govern the issue to be negotiated, such as trade dispute or a salary raise, before haggling about dollars or concessions as though you are in a bazaar. For example, should the primary reference point when hiring new managers be their past salary, your own internal payment scale, or the amount an outside party is offering them? Once you agree on that in principle, the remaining negotiation will be much easier. Also remember that good negotiators spend more time understanding the other side"s hopes, fears, and context than just their own agendas, plus any knowledge asymmetries that might exist.


Tech

Friday, February 16, 2018

Servers? We don't need no stinkin' servers!

Video: IBM"s new tool to develop serverless applications

Read this

What is Docker and why is it so darn popular?

What is Docker and why is it so darn popular?

Docker is hotter than hot because it makes it possible to get far more apps running on the same old servers and it also makes it very easy to package and ship programs. Here"s what you need to know about it.

Read More

OK, so we"ll always need some servers.

But with the rise of virtual machines (VM)s and container technologies such as Docker, combined with DevOps and cloud orchestration to automatically manage ever-larger numbers of server applications, serverless computing is becoming real.

Must read: Serverless computing: The smart person"s guide

We"re a long, long way from the idea that you need one server to run one application.

So, what is serverless computing exactly? According to the Cloud Native Computing Foundation (CNCF) Serverless Working Group (WG):

Serverless computing refers to the concept of building and running applications that do not require server management. It describes a finer-grained deployment model where applications, bundled as one or more functions, are uploaded to a platform and then executed, scaled, and billed in response to the exact demand needed at the moment.

CNCF created the WG to "explore the intersection of cloud native and serverless technology." The first output of the group was a summary of serverless computing projects. These include Apache OpenWhisk, AWS Lambda, Google Cloud Functions, and Azure Cloud Functions. In short, all the major public cloud players are investing in serverless architectures. The vast majority of these are using Kubernetes to orchestrate their activities.

Read also: Top cloud providers 2018: How AWS, Microsoft, Google Cloud Platform, IBM Cloud, Oracle, Alibaba stack up | In a blockbuster container and Kubernetes deal, Red Hat acquires CoreOS

It"s an idea that is gaining fans. In a survey at KubeCon Austin, the most recent of an international series of conferences for Kubernetes users, the CNCF found 41 percent of respondents are already using serverless technology. An additional 28 percent are planning on using it within the next 12 to 18 months. Of the respondents currently using serverless technology, 70 percent are using AWS Lambda, followed by much smaller numbers deploying with Google Cloud Functions, Apache OpenWhisk, and Azure Functions.

Why are they investing in this approach? According to the recently released CNCF WG-Serverless Whitepaper, "Serverless computing does not mean that we no longer use servers to host and run code; nor does it mean that operations engineers are no longer required." But "consumers of serverless computing no longer need to spend time and resources on server provisioning, maintenance, updates, scaling, and capacity planning. Instead, all of these tasks and capabilities are handled by a serverless platform and are completely abstracted away from the developers and IT/operations teams. As a result, developers focus on writing their applications" business logic. Operations engineers are able to elevate their focus to more business critical tasks."

What this means to your executive suite is you"ll be spending less on operations and getting more productive work from your IT staff.

Read also: Serverless but not stress-free: enterprise computing moves outside the enterprise | Microsoft adds support for Java to its Azure Functions serverless-computing service

In practice, this approach can work in two different ways:

  1. Functions-as-a-Service (FaaS) typically provides event-driven computing. Developers run and manage application code with functions that are triggered by events or HTTP requests. Developers deploy small units of code to the FaaS, which are executed as needed as discrete actions, scaling without the need to manage servers or any other underlying infrastructure.
  2. Backend-as-a-Service (BaaS) are third-party API-based services that replace core subsets of functionality in an application. Because those APIs are provided as a service that auto-scales and operates transparently, this appears to the developer to be serverless.

By the CNCF WG"s analysis, this delivers the following benefits to developers:

  1. Zero Server Ops: Serverless dramatically changes the cost model of running software applications through eliminating the overhead involved in the maintenance of server resources. Without provisioning, updating, or managing server infrastructure, a company can save significant overhead costs. In addition, since a serverless FaaS or BaaS can instantly and precisely scale to handle each individual incoming request, the serverless approach automatically scales down the compute resources so that there is never idle capacity.
  2. No Compute Cost When Idle: One of the greatest benefits of the serverless approach from a consumer perspective is that there are no costs resulting from idle capacity. For example, serverless compute services do not charge for idle VM or containers. When there"s no work being done, there are no charges being racked up.

Even more important to the immediate bottom-line savings though, wrote Satwikeshwar Reddy, an AWS architect, is "the biggest advantage of Serverless Architecture (SA) and often over-shadowed by the operational cost savings is the developer time. More accurately, time it takes from an idea to a production ready feature."

That all sounds grand, but does it work?

Read also: Serverless computing takes another step forward | Google releases Cloud TPU beta, GPU support for Kubernetes

Serverless computing, while new as a broadly accepted concept, isn"t new in production. This "pay as you go" model can be traced back to 2006"s short-lived Zimki company. Later, Iron.io, with its Worker container-based distributed work-on-demand platform, enabled customers to realize profits from a serverless approach. Since then, other companies have adopted this approach successfully.

Will a serverless approach work for your company? It"s time to find out and an excellent place to start is with the CNCF white paper. And, who knows, maybe you will be able to say, "Servers? We don"t need no stinkin" servers!" in your next IT planning meeting.

Related stories


Tech

Sunday, January 28, 2018

Don't Quit Your PR Program Unless You've Considered These 3 Things

Whether you are looking to gain awareness, improve SEO, or increase sales, having great exposure can help you get there. But PR is not a band-aid for an overarching business problem--nor is it a get rich fast technique.

A great PR strategy can take many years to build. Over the years, I"ve seen many companies start their efforts, only to stop before they"ve given the program enough time to develop. I"ve heard dozens of marketers and founders explain that they quit their PR efforts after their pitch didn"t get picked up by enough outlets in the first few week. Gaining great coverage takes time, pitch optimization, and persistence.

Often times, if a brand could have taken a step back after a rejected story to tweak their angle and try again, the second story they pitch could have been widely successful. Here"s why you shouldn"t throw in the towel for your PR outreach just yet:

1. Relationships take time to build.

Imagine you are at a party. You immediately start talking about you, your business, and your news. Very quickly, many people will not want to talk with you.

The same holds true when you"re building relationships with the media. It takes time to get to know a reporter and what they are writing about and then creating relevant pitches that are helpful to them. When you build trust and rapport with reporters, they"ll be more likely to open your emails, which is the first step to gaining great coverage.

You can build a better relationship with reporters by becoming well versed with their past writings and looking for opportunities to tell them stories of interest. Take a look through their Twitter accounts and personal websites to learn more about what they"re covering and the news that is important to them.

When you reach out to a reporter for the first time, show them that you are knowledgeable about their area of coverage and that your story fits their angle. When we reach out to reporters we make sure to spend time reading their past work to ensure our pitch is the right fit for their area of expertise.  It can be easy to burn a press bridge simply by not personalizing an email enough--take your time, do your research, and get to know reporters for the long term. Slow and steady wins the race.

2. SEO is a long-term game.

When you receive a press mention, you"ll likely see a spike in traffic on the day it"s published--but don"t discount the future traffic. If you are a mattress company and you get listed as "The Best Mattresses Ever Made," you"ll benefit from both the spike and also later from people who are searching for mattresses and come across the article. Traffic from press articles should be monitored for months to come, even after publication.

An authoritative link will not only drive traffic, but will also help your website in the search engine rankings. This boost will not happen instantly. With time and relevant inbound links, you"ll see not just your referral traffic grow, but also your organic search traffic from Google.

3. Press takes commitment--and a bit of luck.

It takes a while to learn about the best way to pitch your product. Each time you pitch, you"ll learn more about what copy and message resonates with reporters.

If you"re not seeing any success, it does not mean you don"t have an interesting story. It might mean you are pitching to the wrong reporters, your email subject line needs work, or you simply didn"t follow up.

By tracking your emails with a tool like SideKick or Yesware, you"ll be better able to see who is opening your mails, what they"re clicking on, and how many times they went back to the email. You can use this data to refine your pitch the next time. With the media always changing, it also takes a bit of luck to pitch at the right time to the right reporter with the right story.

Pitching takes a strong backbone and you"ll get a lot of rejections. If you haven"t had success yet, keep trying. And if you"ve been pitching for months with still no results, it might be time to call in a PR pro to help you optimize your pitch and press kit.

If you"re looking to reap the benefits of the press, start early, optimize often, and plan your strategy for the long haul. This time next year, you"ll be glad you stuck with it.


Tech