Feature Team Quotes

When I was in high school I asked myself at one point: "Why do I care if my high school's team wins the football game? I don't know anybody on the team, they have nothing to do with me... why am I here and applaud? It does not make any sense." But the point is, it does make sense: It's a way of building up irrational attitudes of submission to authority and group cohesion behind leadership elements. In fact it's training in irrational jingoism. That's also a feature of competitive sports.

Market research is not an add-on feature, it’s a necessity for business survival and business success.

In one of the most cited studies of expert problem solving ever conducted, an interdisciplinary team of scientists came to a pretty simple conclusion: successful problem solvers are more able to determine the deep structure of a problem before they proceed to match a strategy to it. Less successful problem solvers are more like most students in the Ambiguous Sorting Task: they mentally classify problems only by superficial, overtly stated features, like the domain context.

Most inventors and engineers I’ve met are like me—they’re shy and they live in their heads. They’re almost like artists. In fact, the very best of them are artists. And artists work best alone where they can control an invention’s design without a lot of other people designing it for marketing or some other committee. I don’t believe anything really revolutionary has been invented by committee. If you’re that rare engineer who’s an inventor and also an artist, I’m going to give you some advice that might be hard to take. That advice is: Work alone. You’re going to be best able to design revolutionary products and features if you’re working on your own. Not on a committee. Not on a team

You can't take your old organization based on feature teams, roadmaps, and passive managers, then overlay a technique from a radically different culture and expect that will work or change anything.

Next to my green eyes, my blond hair is definitely my best feature. So, out of obligation to all the blondes before me (Cinderella, Sleeping Beauty, the many Barbies I have loved and tortured), I tend to spend hours getting it right. You know, so as not to let down the team.

Most inventors and engineers I’ve met are like me—they’re shy and they live in their heads. They’re almost like artists. In fact, the very best of them are artists. And artists work best alone where they can control an invention’s design without a lot of other people designing it for marketing or some other committee. I don’t believe anything really revolutionary has been invented by committee. If you’re that rare engineer who’s an inventor and also an artist, I’m going to give you some advice that might be hard to take. That advice is: Work alone. You’re going to be best able to design revolutionary products and features if you’re working on your own. Not on a committee. Not on a team.

Finally, it's all about solving problems, not implementing features. Conventional product roadmaps are all about output. Strong teams know it's not only about implementing a solution. They must ensure that solution solves the underlying problem. It's about business results.

Being well regulated in relatedness is the deeply gratifying state that people seek ceaselessly in romance, religions, and cults; in husbands and wives, pets, softball teams, bowling leagues, and a thousand other features of human life driven by the thirst for sustaining affiliations.

If you’re that rare engineer who’s an inventor and also an artist, I’m going to give you some advice that might be hard to take. That advice is: Work alone. You’re going to be best able to design revolutionary products and features if you’re working on your own. Not on a committee. Not on a team.

And that’s how Canning and I came to have a big framed photo on our living room wall featuring the entire Toronto team dressed in very loud gingham. I swear the color rendered a little bolder in print than it looks in real life, because this photo is kind of blinding. But Jamie snickers whenever I suggest that.

Loyalty is not built on features and benefits. Features and benefits do not inspire. Loyalty and long-lasting relationships are based on something deeper.

Work alone. You’re going to be best able to design revolutionary products and features if you’re working on your own. Not on a committee. Not on a team.

Most important, teams working in this system begin to measure their productivity according to validated learning, not in terms of the production of new features.

R&D teams have a tendency to confuse product features with customer benefits. They assume that more features equals more benefits. This is not true.

Our goal is not to create a deliverable or a feature: it’s to positively affect customer behavior or change in the world — to create an outcome.

When he ran a review of his team’s Slack usage, he found that the most popular feature was a plug-in that inserts animated GIFs into the chat conversations.

When we align emotionally with our customers and clients, our connection is much stronger and more meaningful than any affiliation based on features and benefits. That’s what starting with WHY is all about.

Mental health, contemporary psychiatrists tell us, consists of the ability to adapt to the inevitable stresses and misfortunes of life. It does not mean freedom from anxiety and depression, but only the ability to cope with these afflictions in a healthy way. “An outstanding feature of successful adaptation,” writes George Vaillant, “is that it leaves the way open for future growth.” Of course, Abraham Lincoln’s capacity for growth would prove enormous.

I’m going to give you some advice that might be hard to take. That advice is: Work alone. You’re going to be best able to design revolutionary products and features if you’re working on your own. Not on a committee. Not on a team.

Shifting to an outcome mindset is harder than it looks. We spend most of our time talking about outputs. So, it’s not surprising that we tend to confuse the two. Even when teams intend to choose an outcome, they often fall into the trap of selecting an output. I see teams set their outcome as “Launch an Android app” instead of “Increase mobile engagement” or “Get to feature parity on the new tech stack” instead of “Transition customer to the new tech stack.

In place of maps, whiteboards began to appear in our headquarters. Soon they were everywhere. Standing around them, markers in hand, we thought out loud, diagramming what we knew, what we suspected, and what we did not know. We covered the bright white surfaces with multicolored words and drawings, erased, and then covered again. We did not draw static geographic features; we drew mutable relationships—the connections between things rather than the things themselves.

I spent that night lying huddled and shivering in the vast bed of the hotel. My feet were icy, my knees drawn up, my head sideways on the pillow; in front of me the arctic waste of starched white bedsheet stretched out to infinity. I knew I could never traverse it, regain the track, get back to where it was warm; I knew I was directionless; I knew I was lost. I would be discovered years later by some intrepid team—fallen in my tracks, one arm outflung as if grasping at straws, my features desiccated, my fingers gnawed by wolves.

years ago, a Fortune 500 firm was expected to last around seventy-five years. Today this life expectancy is less than fifteen years and is constantly declining. The Fortune 500 list of 2011 featured only sixty-seven companies that appeared on the list of 1955, meaning that just 13.4 percent of the Fortune 500 firms in 1955 were still on the list fifty-six years later. Eighty-seven percent of the companies simply couldn’t keep up; they had either gone bankrupt, merged with other companies, been forced to go private, or fallen off the list completely.

There was no escape: The entire Elliott 503 Mark II software project had to be abandoned, and with it, over thirty man-years of programming effort, equivalent to nearly one man’s active working life, and I was responsible, both as designer and as manager, for wasting it. ... How did we recover from the catastrophe? First, we classified our 503 customers into groups, according to the nature and size of the hardware configurations which they had bought ... We assigned to each group of customers a small team of programmers and told the team leader to visit the customers to find out what they wanted; to select the easiest request to fulfill, and to make plans (but no promises) to implement it. In no case would we consider a request for a feature that would take more than three months to implement and deliver. The project leader would then have to convince me that the customers’ request was reasonable, that the design of the new feature was appropriate, and that the plans and schedules for implementation were realistic. Above all, I did not allow anything to be done which I did not myself understand. It worked! The software requested began to be delivered on the promised dates. With an increase in our confidence and that of our customers, we were able to undertake fulfilling slightly more ambitious requests. Within a year we had recovered from the disaster. Within two years, we even had some moderately satisfied customers.

Define the outcomes you want from your team and its members, and then look for each person’s strength signs to figure out how each person can reach those outcomes most efficiently, most amazingly, most creatively, and most joyfully. The moment you realize you’re in the outcomes business is the moment you turn each person’s uniqueness from a bug into a feature.

The coyotes felt capable, canny, and strangely anthropomorphized, as if they had been endowed with human features by a team of animators. Their hair seemed artfully disheveled, the haircut of a hot, young actor playing a drug addict in an independent film. The coyotes felt more human than most of the humans Sam encountered, more human than Sam himself felt back then.

Mental health, contemporary psychiatrists tell us, consists of the ability to adapt to the inevitable stresses and misfortunes of life. It does not mean freedom from anxiety and depression, but only the ability to cope with these afflictions in a healthy way. “An outstanding feature of successful adaptation,” writes George Vaillant, “is that it leaves the way open for future growth.

Traditionally siloed technical teams interact through complex ticketing systems and ritualistic request procedures, which may require director-level intervention. A team taking a more DevOps approach talks about the product throughout its lifecycle, discussing requirements, features, schedules, resources, and whatever else might come up. The focus is on the product, not building fiefdoms and amassing political power.

When salespeople lead with their product or service, it is impossible to be perceived as consultants or trusted advisors. It makes it as clear as day that the salesperson believes the relationship and sale are centered on his offering, not the customer and its needs. It’s as if the salesperson is begging the customer to put his offering’s features and price on a spreadsheet to be compared against every competitors’ features and price.

Driving exploration is critical, but knowing when to stop is also. Product development is exploring with a purpose, delivering value within a set of constraints. Frequent, timeboxed iterations compel the development and product teams and executives to make difficult tradeoff decisions early and often during the project. Feature delivery contributes to realistic evaluations because product managers can look at tangible, verifiable results.

In East Bangor, Pennsylvania (population 800), there’s a little diner named for the trolley that used to take people to the once-bustling steel town of Bethlehem. The proprietors have adorned the walls with photographs of other local things that are no more. There’s one of the East Bangor band, a group of about twenty men and boys, in uniform, in front of a bandstand draped with bunting. There’s also one of the Kaysers, a local baseball club, on the day of an exhibition ballgame against the Philadelphia Athletics. These were Connie Mack’s A’s, which team in those early 1930s featured Hall of Famers Jimmie Foxx, Mickey Cochrane, and Lefty Grove. How did a village of under a thousand people manage to have its own band? How did a cluster of slate-belt villages field a regular baseball club, apparently good enough to stay on the same field for nine innings with the Philadelphia Athletics? What

Moments of pride commemorate people’s achievements. We feel our chest puff out and our chin lift. 2. There are three practical principles we can use to create more moments of pride: (1) Recognize others; (2) Multiply meaningful milestones; (3) Practice courage. The first principle creates defining moments for others; the latter two allow us to create defining moments for ourselves. 3. We dramatically underinvest in recognition. • Researcher Wiley: 80% of supervisors say they frequently express appreciation, while less than 20% of employees agree. 4. Effective recognition is personal, not programmatic. (“ Employee of the Month” doesn’t cut it.) • Risinger at Eli Lilly used “tailored rewards” (e.g., Bose headphones) to show his team: I saw what you did and I appreciate it. 5. Recognition is characterized by a disjunction: A small investment of effort yields a huge reward for the recipient. • Kira Sloop, the middle school student, had her life changed by a music teacher who told her that her voice was beautiful. 6. To create moments of pride for ourselves, we should multiply meaningful milestones—reframing a long journey so that it features many “finish lines.” • The author Kamb planned ways to “level up”—for instance “Learn how to play ‘Concerning Hobbits’ from The Fellowship of the Ring”—toward his long-term goal of mastering the fiddle.

Jobs spent part of every day for six months helping to refine the display. “It was the most complex fun I’ve ever had,” he recalled. “It was like being the one evolving the variations on ‘Sgt. Pepper.’ ” A lot of features that seem simple now were the result of creative brainstorms. For example, the team worried about how to prevent the device from playing music or making a call accidentally when it was jangling in your pocket. Jobs was congenitally averse to having on-off switches, which he deemed “inelegant.” The solution was “Swipe to Open,” the simple and fun on-screen slider that activated the device when it had gone dormant. Another breakthrough was the sensor that figured out when you put the phone to your ear, so that your lobes didn’t accidentally activate some function. And of course the icons came in his favorite shape, the primitive he made Bill Atkinson design into the software of the first Macintosh: rounded rectangles. In session after session, with Jobs immersed in every detail, the team members figured out ways to simplify what other phones made complicated. They added a big bar to guide you in putting calls on hold or making conference calls, found easy ways to navigate through email, and created icons you could scroll through horizontally to get to different apps—all of which were easier because they could be used visually on the screen rather than by using a keyboard built into the hardware.

The jury was composed of eight blacks and four whites. Hoffa and his attorney, the legendary Edward Bennett Williams, struck only white jurors in the selection process. Hoffa had a black female lawyer flown in from California to sit at counsel table. He arranged for a newspaper, The Afro-American, to run an ad praising Hoffa as a champion of the “Negro race.” The ad featured a photo of Hoffa’s black-and-white legal team. Hoffa then had the newspaper delivered to the home of each black juror. Finally, Hoffa’s Chicago underworld buddy Red Dorfman had the legendary boxing champion Joe Louis flown in from his Detroit home. Jimmy Hoffa and Joe Louis hugged in front of the jury as if they were old friends. Joe Louis stayed and watched a couple of days of testimony. When Cye Cheasty testified, Edward Bennett Williams asked him if he had ever officially investigated the NAACP. Cheasty denied he had, but the seed was planted. Hoffa was acquitted. Edward

Code should be obvious: When someone needs to make a change, they should be able to find the code to be changed easily and to make the change quickly without introducing any errors. A healthy code base maximizes our productivity, allowing us to build more features for our users both faster and more cheaply. To keep code healthy, pay attention to what is getting between the programming team and that ideal, then refactor to get closer to the ideal. But the most important thing to learn from this example is the rhythm of refactoring. Whenever I’ve shown people how I refactor, they are surprised by how small my steps are, each step leaving the code in a working state that compiles and passes its tests. I was just as surprised myself when Kent Beck showed me how to do this in a hotel room in Detroit two decades ago. The key to effective refactoring is recognizing that you go faster when you take tiny steps, the code is never broken, and you can compose those small steps into substantial changes. Remember that—and the rest is silence.

I remember not belonging. I was always Summer’s older sister—the plain one with the red hair and a gap between her front teeth. The first boy I had a crush on said my teeth looked like piano keys. My smile hid behind by hand until one day the captain of the hockey team said I looked like Madonna. It was like instant validation. Mine wasn’t a flaw, it was a feature . . . my unique trademark. I knew then I didn’t want to be perfect nor was my self-esteem tied to any clique. Starla reassuring teenage Willa of the correct perspective on self esteem and self-worth.

Lasseter and his Pixar team had the first half of the movie ready to screen by November 1993, so they brought it down to Burbank to show to Katzenberg and other Disney executives. Peter Schneider, the head of feature animation, had never been enamored of Katzenberg’s idea of having outsiders make animation for Disney, and he declared it a mess and ordered that production be stopped. Katzenberg agreed. “Why is this so terrible?” he asked a colleague, Tom Schumacher. “Because it’s not their movie anymore,” Schumacher bluntly replied. He later explained, “They were following Katzenberg’s notes,

On the day the company starts, there is very limited customer input to a product specification. The company doesn’t know who its initial customers are (but it may think it knows) or what they will want as features. One alternative is to put Product Development on hold until the Customer Development team can find those customers. However, having a product you can demonstrate and iterate is helpful in moving the Customer Development process along. A more productive approach is to proceed with Product Development, with the feature list driven by the vision and experience of the company’s founders.

Rather than making generalized assumptions about what WIP limits should be for each value stream, the Value Stream Network provides the data to determine and tune flow load over time. At Tasktop, we have witnessed this effect by putting too many features that crosscut our architecture on the Hub team. While all of those large and crosscutting features were deemed critical by the business at the time, doing more than one of them in parallel across the teams within that value stream resulted in a lower flow velocity over the course of a year than the flow velocity of taking on one crosscutting feature at a time.

American cold war culture represented an age of anxiety. The anxiety was so severe that it sought relief in an insistent, assertive optimism. Much of American popular culture aided this quest for apathetic security. The expanding white middle class sought to escape their worries in the burgeoning consumer culture. Driving on the new highway system in gigantic showboat cars to malls and shopping centers that accepted a new form of payment known as credit cards, Americans could forget about Jim Crow, communism, and the possibility of Armageddon. At night in their suburban homes, television allowed middle class families to enjoy light domestic comedies like The Adventures of Ozzie and Harriet, Father Knows Best, and Leave It to Beaver. Somnolently they watched representations of settled family life, stories where lost baseball gloves and dinnertime hijinks represented the only conflicts. In the glow of a new Zenith television, it became easy to believe that the American dream had been fully realized by the sacrifice and hard work of the war generation. American monsters in pop culture came to the aid of this great American sleep. Although a handful of science fiction films made explicit political messages that unsettled an apathetic America, the vast majority of 'creature features' proffered parables of American righteousness and power. These narratives ended, not with world apocalypse, but with a full restoration of a secure, consumer-oriented status quo. Invaders in flying saucers, radioactive mutations, and giant creatures born of the atomic age wreaked havoc but were soon destroyed by brainy teams of civilian scientists in cooperation with the American military. These films encouraged a certain degree of paranoia but also offered quick and easy relief to this anxiety... Such films did not so much teach Americans to 'stop worrying and love the bomb' as to 'keep worrying and love the state.

But none of them compared to the dangerous stranger in her room. While the men she was used to were hotter than hell, what they lacked was the fierce aura of power that emanated from this man and his stern, steely features. It was as if he were the deadliest of predators. Feral. That was the only word to do him justice. Surely there wasn’t another soldier in the entire universe who could match him in terms of raw beauty or lethal demeanor. His blond hair was snow white and his features sharp and icy. He wore a pair of black shades that annoyed her since she couldn’t see the upper part of his face or the color of his eyes. Not that it mattered. She saw enough to know that in the land of gorgeous men, he had no competition. As a stark contrast to his white hair, his clothes were a black so deep they seemed to absorb all light, and they were trimmed in silver … No, not silver. Those were weapons tucked into the sleeves and lapels of his ankle-length coat. The left side of it was pulled back, exposing a holstered blaster that was strapped to his left hip. The tall flight boots had silver buckles going up the sides that were fashioned into the image of skulls. At least that’s what she saw at first glance, but as he moved closer she realized those could come off and double as weapons, too. Wow, he was either extremely paranoid or more lethal than a team of League assassins. And that said something.

coyotes were everywhere. He would see them in the front yard, sunning themselves, languorously eating fallen fruit from the cherimoya and loquat trees. He would see them loping down the streets of Silver Lake and Echo Park, sometimes in couples or in families, sorting through the trash outside the vegan place on Sunset, hiking stoically in Griffith Park, nursing their young. The coyotes felt capable, canny, and strangely anthropomorphized, as if they had been endowed with human features by a team of animators. Their hair seemed artfully disheveled, the haircut of a hot, young actor playing a drug addict in an independent film. The coyotes felt more human than most of the humans Sam encountered, more human than Sam himself felt back then. Their constant presence made the city feel wild and dangerous, as if he weren’t living in a city at all.

My name is Professor Ben Fielding and I’d like to invite you to experience our ‘Game’. It remains currently in a Closed Beta stage but will remain in a continual state of ‘live development’. As a dedicated spokesman for a certain kind of Game-world my team and I feel sure that you’ll accept our invitation to try it for yourself, along with the few others in number so far invited. Possible errors and residual bugs together with any suggestions may be reported by vocal commands when you have ‘acclimatised’ to the surroundings. Please ensure that you follow the tutorials for the Interface as you may find it makes potent use of its fully immersive features. Despite anything you may have read or heard about it, we hold high hopes that you will experience it simply as yourself and without pre-conceived notions. Instructions for Fountellion access are as follows…

We tried a number of single-threaded efforts to meet the challenge. We rolled out features one after another, such as a recommendation engine for people that our users should meet and a professional Q&A service. None of them worked well enough to solve the problem. We concluded that the problem might require a Swiss Army knife approach with multiple use cases for multiple groups of users. After all, some people might want a news feed, some might want to track their career progress, and some might be keen on continuing education. Fortunately, LinkedIn had grown to the point where the organization could support multiple threads. We reorganized the product team so that each director of product could focus on a different approach to address engagement. Even though none of those efforts alone proved a silver bullet, the overall combination of them significantly improved user engagement.

Dream Meditation Practices are best performed in an isolated (close to nature) chamber that is clean and dry. Diet should be modified before practice so that solid food is reduced and a sense of lightness is obtained. This meditation is best done after bathing; the student can be nude or wear a light robe. Begin by lying on your back. Focus your mind on the lower tan tien. Summon the spirits residing in the organs by chanting their names in the order of the creation cycle: Houhou or Shen (heart), Beibei or Yi (spleen), Yanyan or Po (lungs), Fu Fu or Zhi (kidneys), and Jianjian or Hun (liver).20 Repeat the chanting and gathering until a bright light and warmth appear in the lower tan tien. Opening this place will automatically open the Microcosmic Orbit. Coordinate your breathing with this meditation to assist the process: inhaling stimulates the kidneys and liver, while exhaling moves the heart and lungs to the centerpoint—the stomach and spleen. Bring the merged five spirits from the lower tan tien (you can also include the other four spirits) up to the heart, and then to the Crystal Palace (also known as the Divine Palace or Hall of Light). The team of merged spirits—now the Yuan Shen or Original Spirit—can exit via the crown. Being conscious during the whole dream, or alternatively remembering the dream after waking, completes the process. You also have the choice of practicing meditation during your dream state. Process the content of the dream during the day, taking any actions in the material world that are now necessary. Remember that one of our goals with the Kan and Li practice is to merge the everyday mind with your dream landscape and meditation. Fusion of these three minds (different from the three tan tiens) is a feature of the developing sage. Ideally, dreaming can include the practice of Microcosmic Orbit, Fusion, and even Kan and Li.

Tom Demarco, a principal of the Atlantic Systems Guild team of consultants ... and his colleague Timothy Lister devised a study called the Coding War Games. The purpose of the games was to identify the characteristics of the best and worst computer programmers; more than six hundred developers from ninety-two different companies participated. Each designed, coded, and tested a program, working in his normal office space during business hours. Each participant was also assigned a partner from the same company. The partners worked separately, however, without any communication, a feature of the games that turned out to be critical. When the results came in, they revealed an enormous performance gap. The best outperformed the worst by a 10:1 ratio. The top programmers were also about 2.5 times better than the median. When DeMarco and Lister tried to figure out what accounted for this astonishing range, the factors that you'd think would matter — such as years of experience, salary, even the time spent completing the work — had little correlation to outcome. Programmers with 10 years' experience did no better than those with two years. The half who performed above the median earned less than 10 percent more than the half below — even though they were almost twice as good. The programmers who turned in "zero-defect" work took slightly less, not more, time to complete the exercise than those who made mistakes. It was a mystery with one intriguing clue: programmers from the same companies performed at more or less the same level, even though they hadn't worked together. That's because top performers overwhelmingly worked for companies that gave their workers the most privacy, personal space, control over their physical environments, and freedom from interruption. Sixty-two percent of the best performers said that their workspace was acceptably private, compared to only 19 percent of the worst performers; 76 percent of the worst performers but only 38 percent of the top performers said that people often interrupted them needlessly.

made some teams much better than others. What they found was that individual intelligence (as measured by IQ) didn’t make the big difference. Having a high aggregate intelligence or just one or two superstars wasn’t critical. The groups that surfaced more and better solutions shared three key qualities. First, they gave one another roughly equal time to talk. This wasn’t monitored or regulated, but no one in these high-achieving groups dominated or was a passenger. Everyone contributed and nothing any one person said was wasted. The second quality of the successful groups was social sensitivity: these individuals were more tuned in to one another, to subtle shifts in mood and demeanor. They scored more highly on a test called Reading the Mind in the Eyes, which is broadly considered a test for empathy. These groups were socially alert to one another’s needs. And the third distinguishing feature was that the best groups included more women, perhaps because that made them more diverse, or because women tend to score more highly on tests for empathy. What this (and much more) research highlights is just how critical the role of social connectedness can be. Reading the research, I

When I started in real estate, despite high ambition, I was constrained by the same 24 hours as everyone else. My early success came from a grueling schedule, long hours, and the high price of near burn-out. In self-defense, I devised a system that featured direct marketing in place of traditional prospecting plus a highly effective team, with all the non-rainmaker tasks delegated to them. This took me to the top of the profession, twice #1 in RE/MAX worldwide in commissions earned, and 15 years as one of the top agents—working less hours than most. While an active agent, I consistently sold over 500 homes a year, even while starting and developing a second business, training and coaching more millionaire agents than any other coach. Without the inspiration of Dan Kennedy’s direct marketing methods and his extraordinary, extreme time-management philosophy, these achievements simply would not have been possible. LEVERAGING yourself, by media in place of manual labor, and with other people is very intimidating to most real estate agents and to most small businesspeople. It frankly is not easy to get right, but it is the quantum leap that uniquely and simultaneously lifts income and supports a great lifestyle. —CRAIG PROCTOR, CRAIGPROCTOR.COM

Launching “Buy It Now” was a large change that touched every transaction, but the eBay team also innovated across the experience for both sellers and buyers as well. With an initial success, we doubled down on innovation to drive growth. We introduced stores on eBay, which dramatically increased the amount of product offered for sale on the platform. We expanded the menu of optional features that sellers could purchase to better highlight their listings on the site. We improved the post-transaction experience on ebay.com by significantly improving the “checkout” flow, including the eventual seamless integration of PayPal on the eBay site. Each of these innovations supported the growth of the business and helped to keep that gravity at bay. Years later, Jeff became a general partner at Andreessen Horowitz, where he would kick off the firm’s success in startups with network effects, investing in Airbnb, Instacart, Pinterest, and others. I’m lucky to work with him! He recounted in an essay on the a16z blog that his strategy was to grow eBay by adding layers and layers of new revenue—like “adding layers to the cake.” You can see it visually here: Figure 12: eBay’s growth layer cake As the core US business began to look more like a line than a hockey stick, international and payments were layered on top. Together, the aggregate business started to look like a hockey stick, but underneath it was actually many new lines of business.

our explosive growth was slowing down our pace of innovation. We were spending more time coordinating and less time building. More features meant more software, written and supported by more software engineers, so both the code base and the technical staff grew continuously. Software engineers were once free to modify any section of the entire code base to independently develop, test, and immediately deploy any new features to the website. But as the number of software engineers grew, their work overlapped and intertwined until it was often difficult for teams to complete their work independently. Each overlap created one kind of dependency, which describes something one team needs but can’t supply for itself. If my team’s work requires effort from yours—whether it’s to build something new, participate, or review—you’re one of my dependencies. Conversely, if your team needs something from mine, I’m a dependency of yours. Managing dependencies requires coordination—two or more people sitting down to hash out a solution—and coordination takes time. As Amazon grew, we realized that despite our best efforts, we were spending too much time coordinating and not enough time building. That’s because, while the growth in employees was linear, the number of their possible lines of communication grew exponentially. Regardless of what form it takes—and we’ll get into the different forms in more detail shortly—every dependency creates drag. Amazon’s growing number of dependencies delayed results, increased frustration, and disempowered teams.

The climate for relationships within an innovation group is shaped by the climate outside it. Having a negative instead of a positive culture can cost a company real money. During Seagate Technology’s troubled period in the mid-to-late 1990s, the company, a large manufacturer of disk drives for personal computers, had seven different design centers working on innovation, yet it had the lowest R&D productivity in the industry because the centers competed rather than cooperated. Attempts to bring them together merely led people to advocate for their own groups rather than find common ground. Not only did Seagate’s engineers and managers lack positive norms for group interaction, but they had the opposite in place: People who yelled in executive meetings received “Dog’s Head” awards for the worst conduct. Lack of product and process innovation was reflected in loss of market share, disgruntled customers, and declining sales. Seagate, with its dwindling PC sales and fading customer base, was threatening to become a commodity producer in a changing technology environment. Under a new CEO and COO, Steve Luczo and Bill Watkins, who operated as partners, Seagate developed new norms for how people should treat one another, starting with the executive group. Their raised consciousness led to a systemic process for forming and running “core teams” (cross-functional innovation groups), and Seagate employees were trained in common methodologies for team building, both in conventional training programs and through participation in difficult outdoor activities in New Zealand and other remote locations. To lead core teams, Seagate promoted people who were known for strong relationship skills above others with greater technical skills. Unlike the antagonistic committees convened during the years of decline, the core teams created dramatic process and product innovations that brought the company back to market leadership. The new Seagate was able to create innovations embedded in a wide range of new electronic devices, such as iPods and cell phones.

SCULLEY. Pepsi executive recruited by Jobs in 1983 to be Apple’s CEO, clashed with and ousted Jobs in 1985. JOANNE SCHIEBLE JANDALI SIMPSON. Wisconsin-born biological mother of Steve Jobs, whom she put up for adoption, and Mona Simpson, whom she raised. MONA SIMPSON. Biological full sister of Jobs; they discovered their relationship in 1986 and became close. She wrote novels loosely based on her mother Joanne (Anywhere but Here), Jobs and his daughter Lisa (A Regular Guy), and her father Abdulfattah Jandali (The Lost Father). ALVY RAY SMITH. A cofounder of Pixar who clashed with Jobs. BURRELL SMITH. Brilliant, troubled hardware designer on the original Mac team, afflicted with schizophrenia in the 1990s. AVADIS “AVIE” TEVANIAN. Worked with Jobs and Rubinstein at NeXT, became chief software engineer at Apple in 1997. JAMES VINCENT. A music-loving Brit, the younger partner with Lee Clow and Duncan Milner at the ad agency Apple hired. RON WAYNE. Met Jobs at Atari, became first partner with Jobs and Wozniak at fledgling Apple, but unwisely decided to forgo his equity stake. STEPHEN WOZNIAK. The star electronics geek at Homestead High; Jobs figured out how to package and market his amazing circuit boards and became his partner in founding Apple. DEL YOCAM. Early Apple employee who became the General Manager of the Apple II Group and later Apple’s Chief Operating Officer. INTRODUCTION How This Book Came to Be In the early summer of 2004, I got a phone call from Steve Jobs. He had been scattershot friendly to me over the years, with occasional bursts of intensity, especially when he was launching a new product that he wanted on the cover of Time or featured on CNN, places where I’d worked. But now that I was no longer at either of those places, I hadn’t heard from him much. We talked a bit about the Aspen Institute, which I had recently joined, and I invited him to speak at our summer campus in Colorado. He’d be happy to come, he said, but not to be onstage. He wanted instead to take a walk so that we could talk. That seemed a bit odd. I didn’t yet

Success comes with an inevitable problem: market saturation. New products initially grow just by adding more customers—to grow a network, add more nodes. Eventually this stops working because nearly everyone in the target market has joined the network, and there are not enough potential customers left. From here, the focus has to shift from adding new customers to layering on more services and revenue opportunities with existing ones. eBay had this problem in its early years, and had to figure its way out. My colleague at a16z, Jeff Jordan, experienced this himself, and would often write and speak about his first month as the general manager of eBay’s US business. It was in 2000, and for the first time ever, eBay’s US business failed to grow on a month-over-month basis. This was critical for eBay because nearly all the revenue and profit for the company came from the US unit—without growth in the United States, the entire business would stagnate. Something had to be done quickly. It’s tempting to just optimize the core business. After all, increasing a big revenue base even a little bit often looks more appealing than starting at zero. Bolder bets are risky. Yet because of the dynamics of market saturation, a product’s growth tends to slow down and not speed up. There’s no way around maintaining a high growth rate besides continuing to innovate. Jeff shared what the team did to find the next phase of growth for the company: eBay.com at the time enabled the community to buy and sell solely through online auctions. But auctions intimidated many prospective users who expressed preference for the ease and simplicity of fixed price formats. Interestingly, our research suggested that our online auction users were biased towards men, who relished the competitive aspect of the auction. So the first major innovation we pursued was to implement the (revolutionary!) concept of offering items for a fixed price on ebay.com, which we termed “buy-it-now.” Buy-it-now was surprisingly controversial to many in both the eBay community and in eBay headquarters. But we swallowed hard, took the risk and launched the feature . . . and it paid off big. These days, the buy-it-now format represents over $40 billion of annual Gross Merchandise Volume for eBay, 62% of their total.65

Similarly, the computers used to run the software on the ground for the mission were borrowed from a previous mission. These machines were so out of date that Bowman had to shop on eBay to find replacement parts to get the machines working. As systems have gone obsolete, JPL no longer uses the software, but Bowman told me that the people on her team continue to use software built by JPL in the 1990s, because they are familiar with it. She said, “Instead of upgrading to the next thing we decided that it was working just fine for us and we would stay on the platform.” They have developed so much over such a long period of time with the old software that they don’t want to switch to a newer system. They must adapt to using these outdated systems for the latest scientific work. Working within these constraints may seem limiting. However, building tools with specific constraints—from outdated technologies and low bitrate radio antennas—can enlighten us. For example, as scientists started to explore what they could learn from the wait times while communicating with deep space probes, they discovered that the time lag was extraordinarily useful information. Wait times, they realized, constitute an essential component for locating a probe in space, calculating its trajectory, and accurately locating a target like Pluto in space. There is no GPS for spacecraft (they aren’t on the globe, after all), so scientists had to find a way to locate the spacecraft in the vast expanse. Before 1960, the location of planets and objects in deep space was established through astronomical observation, placing an object like Pluto against a background of stars to determine its position.15 In 1961, an experiment at the Goldstone Deep Space Communications Complex in California used radar to more accurately define an “astronomical unit” and help measure distances in space much more accurately.16 NASA used this new data as part of creating the trajectories for missions in the following years. Using the data from radio signals across a wide range of missions over the decades, the Deep Space Network maintained an ongoing database that helped further refine the definition of an astronomical unit—a kind of longitudinal study of space distances that now allows missions like New Horizons to create accurate flight trajectories. The Deep Space Network continued to find inventive ways of using the time lag of radio waves to locate objects in space, ultimately finding that certain ways of waiting for a downlink signal from the spacecraft were less accurate than others. It turned to using the antennas from multiple locations, such as Goldstone in California and the antennas in Canberra, Australia, or Madrid, Spain, to time how long the signal took to hit these different locations on Earth. The time it takes to receive these signals from the spacecraft works as a way to locate the probes as they are journeying to their destination. Latency—or the different time lag of receiving radio signals on different locations of Earth—is the key way that deep space objects are located as they journey through space. This discovery was made possible during the wait times for communicating with these craft alongside the decades of data gathered from each space mission. Without the constraint of waiting, the notion of using time as a locating feature wouldn’t have been possible.

How Google Works (Schmidt, Eric) - Your Highlight on Location 3124-3150 | Added on Sunday, April 5, 2015 10:35:40 AM In late 1999, John Doerr gave a presentation at Google that changed the company, because it created a simple tool that let the founders institutionalize their “think big” ethos. John sat on our board, and his firm, Kleiner Perkins, had recently invested in the company. The topic was a form of management by objectives called OKRs (to which we referred in the previous chapter), which John had learned from former Intel CEO Andy Grove.173 There are several characteristics that set OKRs apart from their typical underpromise-and-overdeliver corporate-objective brethren. First, a good OKR marries the big-picture objective with a highly measurable key result. It’s easy to set some amorphous strategic goal (make usability better … improve team morale … get in better shape) as an objective and then, at quarter end, declare victory. But when the strategic goal is measured against a concrete goal (increase usage of features by X percent … raise employee satisfaction scores by Y percent … run a half marathon in under two hours), then things get interesting. For example, one of our platform team’s recent OKRs was to have “new WW systems serving significant traffic for XX large services with latency < YY microseconds @ ZZ% on Jupiter.”174 (Jupiter is a code name, not the location of Google’s newest data center.) There is no ambiguity with this OKR; it is very easy to measure whether or not it is accomplished. Other OKRs will call for rolling out a product across a specific number of countries, or set objectives for usage (e.g., one of the Google+ team’s recent OKRs was about the daily number of messages users would post in hangouts) or performance (e.g., median watch latency on YouTube videos). Second—and here is where thinking big comes in—a good OKR should be a stretch to achieve, and hitting 100 percent on all OKRs should be practically unattainable. If your OKRs are all green, you aren’t setting them high enough. The best OKRs are aggressive, but realistic. Under this strange arithmetic, a score of 70 percent on a well-constructed OKR is often better than 100 percent on a lesser one. Third, most everyone does them. Remember, you need everyone thinking in your venture, regardless of their position. Fourth, they are scored, but this scoring isn’t used for anything and isn’t even tracked. This lets people judge their performance honestly. Fifth, OKRs are not comprehensive; they are reserved for areas that need special focus and objectives that won’t be reached without some extra oomph. Business-as-usual stuff doesn’t need OKRs. As your venture grows, the most important OKRs shift from individuals to teams. In a small company, an individual can achieve incredible things on her own, but as the company grows it becomes harder to accomplish stretch goals without teammates. This doesn’t mean that individuals should stop doing OKRs, but rather that team OKRs become the more important means to maintain focus on the big tasks. And there’s one final benefit of an OKR-driven culture: It helps keep people from chasing competitors. Competitors are everywhere in the Internet Century, and chasing them (as we noted earlier) is the fastest path to mediocrity. If employees are focused on a well-conceived set of OKRs, then this isn’t a problem. They know where they need to go and don’t have time to worry about the competition. ==========

Windows apps development company india Windows Application Development Company in India help you to gain response from the users and customers effectively. This operating system can be one of the best platforms to showcase your possibilities. Although there are numerous windows apps development companies in India, our team stands apart to deliver the right solutions. The users in the windows platform look forward to apps that deliver exciting features and experience.

facebook game development india FuGenX, a leading Facebook game development company India, the technical team provides a real world gaming experience. Our Facebook app developers integrate exciting features to enjoy the pleasure of playing games with real identities, that can offer rich competition among other Facebook game development companies in India. We take you through the journey of addictive gaming thrill with all the audio visual effects and allow you to make use of the well-known interactive and responsive features, on the social networking site.

We wanted to change Google’s developer culture to include testing as part of every feature developer’s responsibility. They shared their positive experiences with testing and encouraged teams to write tests. Some teams were interested, but didn’t know how to start. Others would put “improve testing” on their team objectives and key results (OKRs),14 which isn’t always actionable. It was like putting “lose weight” on your New Year’s resolutions. That’s a fine, lofty goal, but if that’s all you say, don’t be surprised if it never happens.

The other feature of this list is that many of these signals could easily be viewed as obvious and redundant. For instance, do highly experienced professionals like nurses and anesthesiologists really need to be explicitly told that their role in a cardiac surgery is important? Do they really need to be informed that if they see the surgeon make a mistake, they might want to speak up? The answer, as Endmondson discovered, is a thundering yes. The value of those signals is not their information but in the fact that they orient the team to the task and to one another. What seems like repetition is, in fact, navigation.

Bill Campbell developed an excellent methodology for measuring executives in a balanced way that will help you achieve this. He breaks performance down into four distinct areas: 1. Results against objectives Once you’ve set a high standard, it will be straightforward to measure your executive against that standard. 2. Management Even if an executive does a superb job achieving her goals, that doesn’t mean she is building a strong and loyal team. It’s important to understand how well she is managing, even if she is hitting her goals. 3. Innovation It’s quite possible for an executive to hit her goal for the quarter by ignoring the future. For example, a great way for an engineering manager to hit her goals for features and dates is by building a horrible architecture, which won’t even support the next release. This is why you must look beyond the black-box results and into the sausage factory to see how things get made. 4. Working with peers This may not be intuitive at first, but executives must be effective at communicating, supporting, and getting what they need from the other people on your staff. Evaluate them along this dimension.

Remarkably, in the vast majority of companies (not the ones that are good at product), the actual product teams don't do much ideation themselves. This is because what's really going on is that the ideas are already handed to the product teams in the form of prioritized features on product roadmaps, where most of the items on those roadmaps are coming either from requests from big customers (or prospective customers), or from company stakeholders or execs. Unfortunately, these are rarely the quality of ideas we're looking for.

With the lens of Jobs to Be Done, the Medtronic team and Innosight (including my coauthor David Duncan) started research afresh in India. The team visited hospitals and care facilities, interviewing more than a hundred physicians, nurses, hospital administrators, and patients across the country. The research turned up four key barriers preventing patients from receiving much-needed cardiac care: Lack of patient awareness of health and medical needs Lack of proper diagnostics Inability of patients to navigate the care pathway Affordability While there were competitors making some progress in India, the biggest competition was nonconsumption because of the challenges the Medtronic team identified. From a traditional perspective, Medtronic might have doubled down on doctors, asking them about priorities and tradeoffs in the product. What features would they value more, or less? Asking patients what they wanted would not have been top of the list of considerations from a marketing perspective. But when Medtronic revisited the problem through the lens of Jobs to Be Done, Monson says, the team realized that the picture was far more complex—and not one that Medtronic executives could have figured out from pouring over statistics of Indian heart disease or asking cardiologists how to make the pacemaker better. Medtronic has missed a critical component of the Job to Be Done.

Rather than asking customers explicitly about feature X, Y or Z, one approach to defining the MVP is to ask, “What is the smallest or least complicated problem that the customer will pay us to solve?” This approach runs counter to the typical cry for more features, which is often based on what the competitors have or what the last customer visited had to say. The MVP is the inverse of what most sales and marketing groups ask of their development teams.

Many people report that the greatest fear they face today is the fear of not having enough money to maintain their lifestyle throughout retirement. Does this sound like you? Social Security is still a vital role in retirement income. The greatest benefit Social Security provides is regular income that is guaranteed to increase over time and continue as long as you live. Keep in mind, Social Security taxes are just that – taxes. As a result, a worker’s retirement security is entirely dependent upon political decisions. Nevertheless, for now, this benefit makes Social Security one of the most valuable sources of income during one’s retirement. Unfortunately, most Americans do not know much about Social Security. They know even less about how to maximize the benefits that may help sustain them throughout retirement. Whether you are depending upon Social Security to make a significant impact on your retirement income or just a part of your entire financial portfolio, it would be wise to understand which claiming options are available to get the most out of your Social Security income. Even in these tough times and volatile markets, we help our clients take a comprehensive approach to their retirement planning. We offer a complimentary service that we call Social Security Maximization or SSI Max. There are hundreds of ways to claim your Social Security, but which one is right for you and your family? One simple mistake or misjudgment of the program can cost you thousands of dollars that you rightfully deserve. Download our free eBook: 4 Myths about Social Security Income to learn a few common misconceptions about Social Security Income. Find out your SSI Max Strategy Our team of experts use a proprietary system that links to the government’s official Social Security website. It only takes a few minutes to generate your SSI Max Report. Click here to see a sample report and act quickly to get your very own personalized report. Just schedule a call with me to find out your very own, optimal SSI Max Strategy! Click here to schedule now! P.S. – Be sure to ask me about including a “Shortfall Analysis” in your report. Our clients are LOVING this feature! Seriously! What is it? Our Advanced Case Design team builds a comprehensive financial plan best suited for your specific situation by considering all of your retirement vehicles. This is, without a doubt, the best retirement planning offer you will see in a very, very long time!

Love MINECRAFT? **Over 18,000 words of kid-friendly fun!** This high-quality fan fiction fantasy diary book is for kids, teens, and nerdy grown-ups who love to read epic stories about their favorite game! Meet the Skull Kids. They're three Minecraft players who hop from world to world, hunting zombies and searching for the elusive Herobrine--the ghost in the machine. Teleporting down into a new world, the group is surprised to find that the game has changed once again, rendering almost ALL of their technology and mods useless. And when two of the Skull Kids are starving and distracted by exploring a desert village on Day 1 of their new adventure, the whole group is in danger when the sun goes down. Will the Skull Kids survive? Thank you to all of you who are buying and reading my books and helping me grow as a writer. I put many hours into writing and preparing this for you. I love Minecraft, and writing about it is almost as much fun as playing it. It’s because of you, reader, that I’m able to keep writing these books for you and others to enjoy. This book is dedicated to you. Enjoy!! After you read this book, please take a minute to leave a simple review. I really appreciate the feedback from my readers, and love to read your reactions to my stories, good or bad. If you ever want to see your name/handle featured in one of my stories, leave a review and tell me about it in there! And if you ever want to ask me any questions, or tell me your idea for a cool Minecraft story, you can email me at steve@skeletonsteve.com. Are you on my Amazing Reader List? Find out at the end of the book! June 29th, 2016 Now I’m going to try something a little different. Tell me what you guys think! This ‘Players Series’ is going to be a continuing series of books following my new characters, the players Renzor51, Molly, and quantum_steve. Make sure to let me know if you like it or not! Would you still like to see more books about mobs? More books about Cth’ka the Creeper King? I’m planning on continuing that one. ;) Don’t forget to review, and please say hi and tell me your ideas! Thanks, Ryan Gallagher, for the ideas to continue the wolf pack book! Enjoy the story. P.S. - Have you joined the Skeleton Steve Club and my Mailing List?? You found one of my diaries!! This particular book is the continuing story of some Minecraft players—a trio of friends who leap from world to world, searching for the elusive Herobrine. They’re zombie hunters and planeswalkers. They call themselves “The Skull Kids”. Every time these Skull Kids hop into a new world, they start with nothing more than the clothes they’re wearing, and they end up dominating the realm where they decide to live. What you are about to read is the first collection of diary entries from Renzor51, the player and member of the Skull Kids who documents their adventures, from the day they landed on Diamodia and carved out their own little empire, and beyond. Be warned—this is an epic book! You’re going to care about these characters. You’ll be scared for them, feel good for them, and feel bad for them! It’s my hope that you’ll be sucked up into the story, and the adventure and danger will be so intense, you’ll forget we started this journey with a video game! With that, future readers, I present to you the tale of the Skull Kids, Book 1. The Skull Kids Ka-tet Renzor51 Renzor51 is the warrior-scribe of the group, and always documents the party’s adventures and excursions into game worlds. He’s a sneaky fighter, and often takes the role of a sniper, but can go head to head with the Skull Kids’ enemies when needed. A natural artist, Renzor51 tends to design and build many of the group’s fortresses and structures, and keeps things organized. He also focuses a lot on weapon-smithing and enchanting, always seeking out ways to improve his gear. Molly

You go to an auto show and see some glamorous and wildly innovative concept car on display and you think, “I’d buy that in a second.” And then five years later, the car finally comes to market and it’s been whittled down from a Ferrari to a Pinto—all the truly breakthrough features have been toned down or eliminated altogether, and what’s left looks mostly like last year’s model. The same sorry fate could have befallen the iPod as well: Ive and Jobs could have sketched out a brilliant, revolutionary music player and then two years later released a dud. What kept the spark alive? The answer is that Apple’s development cycle looks more like a coffeehouse than an assembly line. The traditional way to build a product like the iPod is to follow a linear chain of expertise. The designers come up with a basic look and feature set and then pass it on to the engineers, who figure out how to actually make it work. And then it gets passed along to the manufacturing folks, who figure out how to build it in large numbers—after which it gets sent to the marketing and sales people, who figure out how to persuade people to buy it. This model is so ubiquitous because it performs well in situations where efficiency is key, but it tends to have disastrous effects on creativity, because the original idea gets chipped away at each step in the chain. The engineering team takes a look at the original design and says, “Well, we can’t really do that—but we can do 80 percent of what you want.” And then the manufacturing team says, “Sure, we can do some of that.” In the end, the original design has been watered down beyond recognition. Apple’s approach, by contrast, is messier and more chaotic at the beginning, but it avoids this chronic problem of good ideas being hollowed out as they progress through the development chain. Apple calls it concurrent or parallel production. All the groups—design, manufacturing, engineering, sales—meet continuously through the product-development cycle, brainstorming, trading ideas and solutions, strategizing over the most pressing issues, and generally keeping the conversation open to a diverse group of perspectives. The process is noisy and involves far more open-ended and contentious meetings than traditional production cycles—and far more dialogue between people versed in different disciplines, with all the translation difficulties that creates. But the results speak for themselves.

His features were Middle Eastern, his eyes haunted but also defiant. They were all defiant, Gray had found. When he looked at someone like al-Omari, Gray couldn’t help but think of a Dostoyevsky creation, the displaced outsider, brooding, plotting and methodically stroking a weapon of anarchy. It was the face of a fanatic, of one possessed by a deranged evil. It was the same type of person who’d taken away forever the two people Gray had loved most in the world. Though al-Omari was thousands of miles away in a facility only a very few people even knew existed, the picture and sound were crystal clear thanks to the satellite downlink. Through his headset he asked al-Omari a question in English. The man promptly answered in Arabic and then smiled triumphantly. In flawless Arabic Gray said, “Mr. al-Omari, I am fluent in Arabic and can actually speak it better than you. I know that you lived in England for years and that you speak English better than you do Arabic. I strongly suggest that we communicate in that language so there is absolutely no misunderstanding between us.” Al-Omari’s smile faded, and he sat straighter in his chair. Gray explained his proposal. Al-Omari was to become a spy for the United States, infiltrating one of the deadliest terrorist organizations operating in the Middle East. The man promptly refused. Gray persisted and al-Omari refused yet again, adding that “I have no idea what you’re talking about.” “There are currently ninety-three terrorist organizations in the world as recognized by the U.S. State Department, most of them originating in the Middle East,” Gray responded. “You have confirmed membership in at least three of them. In addition, you were found with forged passports, structural plans to the Woodrow Wilson Bridge and bomb-making material. Now you’re going to work for us, or it will become distinctly unpleasant.” Al-Omari smiled and leaned toward the camera. “I was interrogated years ago in Jordan by your CIA and your military and your FBI, your so-called Tiger Teams. They sent females in wearing only their underwear. They wiped their menstrual blood on me, or at least what they called their menstrual blood, so I was unclean and could not perform my prayers. They rubbed their bodies against me, offered me sex if I talk. I say no to them and I am beaten afterward.” He sat back. “I have been threatened with rape, and they say I will get AIDS from it and die. I do not care. True followers of Muhammad do not fear death as you Christians do. It is your greatest weakness and will lead to your total destruction. Islam will triumph. It is written in the Qur’an. Islam will rule the world.

U4NBA News: Notice The Version Of NBA 2K18 Is For You NBA 2K18 is scheduled to debut on store shelves until September 15th for those that who pre-order. It'll come to Xbox One, PS4, Windows PCs and mobile. You must have noticed some NBA 2K18 version informations to help you to decide which version of NBA 2K18 is the one to pre-order now or purchase on release day. NBA 2K18 Standard Edition NBA 2K18 Standard Edition is for mild fans of the series that don't care as much about Virtual Currency as they do getting access four-days before everyone else. Standard Edition is $59.99. Buyers get 5,000 in Virtual Currency, 10 Weeks of MyTeam Packs and some MyTeam themed cosmetic items for use in the game. This version will come to the Xbox 360, Xbox One, PS4, PS3, PCs and the Nintendo Switch. This version of the game gets you access to the NBA 2K18 Early Tip-Off Weekend, provided you place a pre-order before September 15th. Also Read: Kyrie Irving Will Grace The Cover Of The Standard Edition Of NBA 2K18 NBA 2K18 Legend Edition NBA 2K18 Legend Edition is the upgraded version of the standard game and the version is for big-time fans of Shaq. It’s also for anyone that loves MyCareer and wants an early jumpstart to their character. It doesn’t come with any exclusive features. Instead, it packs Virtual Currency that could make starting out in MyCareer a little easier. Legend Edition is $99.99. There's 100,000 in Virtual Currency included with Legend Edition. Again, you can use Virtual Currency to buy upgrades for your character in the game. The more Virtual Currency you have, the easier it’ll be to get extras in MyCareer. Character add-ons include a Shaq Championship Ring, Shaq Attaq shoes, Shaq Jerseys and Shaq clothing. There are 20 weeks of MyTeam Packs instead of the 10 that the basic version comes with. Physical copies of this game come with 5 Panini cards, Shaq MyTeam Stickers and a poster. Xbox One, PS4, PCs and the Nintendo Switch will get this version. This version qualifies for Early Tip-Off Weekend. NBA 2K18 Legend Edition Gold NBA 2K18 Legend Edition Gold is for the player that enjoys the series year after year and will find themselves spending hours across MyCareer and MyTeam modes for a long time. It’s also for the fan that loves basketball games and doesn’t have a lot of free time to dump into the game to earn Virtual Currency. This version costs $149.99, the most that any version of the game does. Shoppers get 250,000 in Virtual Currency when they buy Legend Edition Gold. There's 40 weekly MyTeam Packs. Developers guaranteed that players who own those packs can get at least one of Shaq and a TEAM 2K Card. Buyers also get the Shaq Attaq Shoes, the championship ring and Shaq Themed Jerseys and apparel. Physical add-ons include a poster, 10 Panini Cards, Shaq MyTeam Stickers and a lenticular printing. Nintendo Switch, Xbox One, Windows PCs and PS4 will get this version. The game qualifies for Early Tip-Off Weekend. In order meet player's demand for NBA 2K18 MT during Early Tip-Off Weekend, we decide to bring forward the activity where offers coupon code "NBA2017". You can buy NBA 2K18 MT from now on to gain up to 5% off.

NBA 2K18 Wishlist - Good Badges To Deal Problems In 2K17 The NBA 2K18 release date has basketball fans hyped. The new game in the series will be the definitive way for fans to take control of their favorite franchises and players on the Xbox One and PS4. As of the features player wish to be added into NBA 2K18, we can compare it with NBA 2K17. Today, we'll list the best badges players would like to see in the latest NBA franchise. Flashy Dunker 2K Sports has spent a large amount of time recording flashy dunk animations that look great when they trigger. Unfortunately players do not equip any of these because they get blocked at a higher rate than the basic one and two hand dunk packages. NBA 2K17 has posterizer to help with contact dunks but Flashy Dunker would be for non-contact animations. The badge would allow you to use these flashy dunk packages in traffic while getting blocked at a lower rate in NBA 2K18. Bullet Passer Badge Even with a high passer rating and Hall of Fame dimer you can still find yourself throwing slow lob passes inexplicably. These passes are easy to intercept and give the defense too much time to recover. Bullet Passer would be an increase in the speed of passes that you throw, allowing you to create open looks for teammates in 2K18 that were not possible in NBA 2K17. A strong passing game is more important than ISO ball and this badge would help with that style of play. 3 And D Badge The 3 and D badge would be an archetype in NBA 2K18 ideally but a badge version would be an acceptable substitute. This badge would once again reward players for playing good defense. The badge would trigger after a block, steal, or good shot defense and would lead to an increase in shooting percentage on the next possession from behind the 3 point arc. Dominant Post Presence Badge It's a travesty that post scorer is one of the more under-utilized archetypes in NBA 2K17. Many players that have created a post scorer can immediately tell you why they do not play it as much as their other MyPlayers, it is incredibly easy to lose the ball in the post. Whether it is a double team or your matchup, getting the ball poked loose is a constant problem. Dominant Post Presence would trigger when you attempt to post up and would be an increase in your ability to maintain possession of the ball as long as NBA 2K18 add this badge. In addition the badge would be an increase in the shooting percentage of your teammate when you pass out of the post to an open man. The Glove NBA 2K17 has too many contested shots. The shot contest rating on most archetypes is not enough to outweigh the contested midrange or 3 point rating and consistently force misses. It's obviously that height helps you contest shots in a major way but it also slows you down. However, the Glove would solve this problem in NBA 2K18. This badge would increase your ability to contest shots effectively, forcing more misses and allowing you to play better defense. Of course, there should be more other tips and tricks for NBA 2K18. If you have better advices, tell us on the official media. The NBA 2K18 Early Tip-Off Weekend starts September 15th. That's a total of four days for dedicated fans to get in the game and try its new features before other buyers. The game is completely unlocked for Early Tip-Off Weekend. Be sure to make enough preparation for the upcoming event.

The Trade Scatto Short Sleeve Jersey is the perfect blend of aerodynamic and technical fabrics. This jersey takes advantage of the fabrics and features from our FR-C collection combined with the fit of our Silver Line Jersey. The materials utilized are ideal for the sublimation process, providing Giordana's Designers and design partners with a high tech canvas on which they can create a wide range of graphics with impeccable detailing. This is what makes The Trade Category of Garments so much fun. Unique sublimated graphics help you stand out from your local group ride, crit, or gran fondo while enjoying the comfort and performance you'd expect from a Giordana Garment Tech Specs: • Gi27: front and side panels • Asteria 2.0: sleeves and shoulders • Doubled Asteria 2.0 arm cuffs • Host Carbon: back panel to support the pockets and prevent sagging • Two reflective strips along the centre jersey pocket • Gripper elastic at waist • CamLock Zipper • Fourth zippered pocket

Prioritization is one of the product manager’s most important functions at this point; if the team were to fix every bug and build every new feature idea, the product would never launch. The

Alpha: At this milestone, key gameplay functionality is implemented, assets are 40–50% final (the rest are placeholders), the game runs on the correct hardware platform in debug mode, and there is enough working to provide the team with a feel for the game. Features might undergo major adjustments at this point, based on play-testing results and other feedback. Alpha occurs 8 to 10 months before code release.

This is because what's really going on is that the ideas are already handed to the product teams in the form of prioritized features on product roadmaps, where most of the items on those roadmaps are coming either from requests from big customers (or prospective customers), or from company stakeholders or execs. Unfortunately, these are rarely the quality of ideas we're looking for. In general, if the product team is given actual business problems to solve rather than solutions, and the product team does their job and interacts directly and frequently with actual users and customers, then getting a sufficient quantity and quality of product ideas is not really a problem.

Leah Pearlman, who was a product manager on the team that developed the “Like” button for Facebook (she was the author of the blog post announcing the feature in 2009), has become so wary of the havoc it causes that now, as a small business owner, she hires a social media manager to handle her Facebook account so she can avoid exposure to the service’s manipulation of the human social drive. “Whether there’s a notification or not, it doesn’t really feel that good,” Pearlman said about the experience of checking social media feedback. “Whatever we’re hoping to see, it never quite meets that bar.

In movies, they drag them across the floor, leaving behind a wide trail of blood. They shut them in trunks. They drive out to deserts, toss suitcases into rivers, call out teams of villains with attractive distorted features to do their dirty work. They leave evidence that no one finds, because there is a team to clear the set between locations. And the corpses are gorgeous, bruises and scars carefully applied by a team of artists to match an overall aesthetic: the magnificent, the haunting dead.

Bad fit customers and technical support There is a line between helping a customer and building custom software for them. You want to avoid one-off features because the effort to build one custom feature is the same effort to help ten good fit customers. If a customer requires custom work, then they are usually a poor fit. These bad customers will drain the life from your team and these customers redirect resources from critical tasks, such as mandatory upgrades, and helping good fit customers succeed. Enough bad customers can cause low employee morale and high turn-over in any department. Here are the differences between good and bad fit customers: Good Customer Traits Bad Customer Traits Software performs the features that he needs Constantly emails about missing features An attractor that leaves reviews, case studies Rude or unpleasant over the phone, a detractor Entry level staff members provide support Senior level staff provides technical support Requires a short call to set-up and configure Requires coding changes and tons of phone support Company is organized Company is a mess Fits into an ideal customer profile Fits into no customer profile Feels like a good fit You get a bad feeling about the company

Your software developers can get bogged down in answering tickets by changing code. This will prevent you from assigning them to projects that will have a bigger impact. In 2021, QuickBooks made an update to how we sync with QuickBooks Desktop. The change allowed us to sync faster and more reliably, and would reduce our support tickets. Since our goal was reducing tickets by 10% and reducing churn, I assigned the project to my team. How does this project relate to the company’s overall goals? Will making this change adversely affect other people? What is the cost and benefit analysis? Some product management tools can link your CRM and feature requests together. They can show the total cost to build the feature and the amount of revenue you will gain, a cost and benefits analysis.

Another challenge with using the microservice architecture is that deploying features that span multiple services requires careful coordination between the various development teams. You have to create a rollout plan that orders service deployments based on the dependencies between services. That’s quite different than a monolithic architecture, where you can easily deploy updates to multiple components atomically.

Best Season for Hair Removal has Arrived! Here at Ulike, we love to nerd out over every hair removal detail. Our team of experts explores the science behind smooth and beautiful skin, so you can focus on the results! According to the study, starting IPL during the "Anagen phase" (also known as Fall by normal people) is the best time to break your hair’s growth cycle for longer-lasting effects. Meanwhile, the clothing we wear during fall can cover our skin from deadly UV light to get a better result. Therefore, start your IPL treatment now, and shine like a million dollars in summer. Can I Achieve Permanent Effect At Home? Yes, you can! People want to solve the hair removal issue once and for all. And this is what Ulike's IPL hair removal can do. With many years of experience developing home-use IPL devices, Ulike's IPL hair removal handset is capable of producing 19.8J of high energy (energy density 6J/cm²) to bring better and faster permanent results within 4-6 weeks. Ulike's product adapts clinical-grade sapphire ice-touch technology that can effectively lower the epidermal temperature of the effective area to 50°F~104°F while emitting high-energy light simultaneously, effectively avoiding burning and pain during use. In comparison, most hair removal devices on the market light window reached temperatures of 158°F~212°F during use, hence having a sense of burning. Will it Cost More? No! It Only Cost Less! Compared with Ulike at-home hair removal and clinic hair removal, both methods can achieve permanent hair removal, and both adapted sapphire Ice-Cooling technology. BUT, The Ulike IPL hair remover can provide you with more privacy and sanitation with only 2.5% cost of doing hair removal in a clinic. Ulike Sapphire AIR White IPL Hair Removal Handset at the price of $309 Main Features: Painless hair removal by Sapphire Ice-Cooling technology Savings more than $10k expense than hair removal at a beauty salon Salon-Grade hair removal in the comfort of your own home Safety and hygiene are guaranteed with no skin damage Easy to sensitize with its flat window design Treat all body parts' hair with five intensity levels 284grams ultra-light compact design for travel convenience

The easiest way to describe how to harness the galvanizing power of why is with a tool I call the belief statement. For example, most of Apple’s product launches in recent years feature slick videos with commentary from Apple designers, engineers, and executives. These videos, while camouflaged as beautiful product showcases, are actually packed with statements not about what the products do but about the design thinking behind them: in essence, the tightly held beliefs with which Apple’s design team operates. We believe our users should be at the center of everything we do. We believe that a piece of technology should be as beautiful as it is functional. We believe that making devices thinner and lighter but more powerful requires innovative problem solving. Belief statements like these are so compelling for two reasons. First, the right corporate or organizational beliefs have the ability to resonate with our personal belief systems and feelings, and move us to action. In fact, the 2018 Edelman Earned Brand study revealed that nearly two out of three people are now belief-driven buyers.4 And as we saw in our discussion of buyers’ emotional motivators in chapter 3, this works even if the beliefs stated are aspirational. For example, if my vision for my future self is someone who weighs a few pounds less and is in better physical shape, a well-timed ad from a health club or fancy kitchen blender evangelizing the benefits of a healthy lifestyle may be enough to rapidly convert me. In the case of Apple, the same phenomenon results in mobs of smitten consumers arriving at stores in droves, braving long lines and paying premium prices, as if to say, “Yes! I do believe I should be at the center of everything you do! Technology should be beautiful! Thinner? Lighter? More powerful? Of course! We share the same vision! We’re both cool!” (Although these actual words are rarely spoken aloud.) The second reason belief statements are so compelling is because they help us manifest the conviction and emotion critical to delivering our message in an authentic way.

Like the decision about Highlander and IntenseDebate, there is no perfect answer. After years of leading projects, the best thing I've learned is that I have to periodically shift between thinking small (bazaar) and thinking long term (cathedral). Asking my team, “If we do these three features in a row, how do they build together into something better than the sum of the parts?” I don't want them fixated on thinking that far ahead, but I do want them to raise their heads and look to the horizon periodically, because that glance improves how they'll evaluate whatever they're building today.

the project board contains feature cards, and each feature team has their own board with the features they are working on plus the associated task breakdown.

To begin the discussion of the Tipping Point, I’ll start with a prominent strategy, “Invite-Only,” that is often used to suck in a large network through viral growth. Another method to tip over a market is with a “Come for the Tool, Stay for the Network” strategy. Take Dropbox, for instance, which is initially adopted by many people for file backup and keeping files synced up between work and home computers—this is the tool. But eventually, a more advanced and stickier use case emerges to share folders with colleagues—this is the network. And if that doesn’t work, some products can always just spend money to build out their network, with a strategy of just “Paying Up for Launch.” For many networked products that touch transactions like marketplaces, teams can just subsidize demand and spend millions to stimulate activity, whether that’s in paying content creators for your social network, or subsidizing driver earnings in rideshare. If the hard side of the network isn’t yet activated, a team can just fill in their gaps themselves, using the technique of “Flintstoning”—as Reddit did, submitting links and content until eventually adding automation and community features for scale. In the end, all of these strategies require enormous creativity. And to close out the Tipping Point section of the book, I introduce Uber’s core ethos of “Always Be Hustlin’”—describing the creativity and decentralized set of teams, all with its own strategies that were localized to each region. Sometimes adding the fifth or one hundredth network requires creativity, product engagements, and tactical changes. In the goal of reaching the Tipping Point, teams must be fluid to build out a broad network of networks.

We would get those insights a lot of the time by visiting customers, which is the best. Because we want to see their of office, who sits next to them, if they’re in a cubicle, what’s in their cubicle, what do they have printed out that’s hung on the wall, what does their browser look like, what are their favorites, what’s on their desktop? You just really want to understand, as a researcher, what are they doing? What does their day look like? And the reason why I care so much about that is because rarely do you get that information when you ask someone a pointed question about features or functions or things that they need. A lot of the times we found that the information we were getting when we asked customers directly was kind of aspirational: It was things that they thought that they wanted or that they dreamed of, but when we looked at what they actually did each day, in most cases it had zero overlap. So we learned way more by having those interviews and watching what they were doing, and seeing their daily practice, and seeing how they had to go through ve different apps to do something, or download something into Excel. Excel was gold for us. It’s always been for me, building the kind software that I do. As soon as I see a customer or prospect use Excel, I know we’re onto something. That’s where they’re doing something that we can help them do more efficiently. But it’s something that almost no customer is going to tell you about. Because it’s so boring to tell someone that: “I download this, I export this, I put it in Excel, and I sort it this way, and I do that, then I put it here, then I do this, then I re-upload it here, then I put it in PowerPoint ...

Call center solutions for small business What does it mean to develop a call center solutions that is small business friendly? It is unique to each organisation, which necessitates that the design be designed on a case-by-case basis. Do you have a partner who is willing to help you build your solution from the ground up? Scaling is a crucial aspect of developing a call center solution for a small organisation. Tiny businesses aren't always small businesses. By the end of a single year, a company that accepts a few dozen calls per week may be taking several hundred calls per day — Alternatively, they could remain the same size. It depends on a number of things, one of which is whether they are committed to providing the resources their customers and employees require for organic growth. Speak with your technology solutions provider about scalability if you want to provide your company the chance to expand. ChaseData offers a variety of scalability alternatives, including solutions that allow for remote agent flexibility, allowing your team to grow and shrink as needed. That way, you'll always be in control of your labour costs, and you'll have the correct number of employees on hand to handle whatever your customer base throws at you! Small Business Still Be Smart A prevalent assumption is that small business call center solutions must be limited in terms of features and capabilities. This is absolutely not the case. When it comes to the technology employed in today's call centers, small can be mighty. One of the most pressing concerns when it comes to increasing efficiency and productivity in a call center – whether large or small – is reducing time spent on repetitive information. Consumers frequently say that they spend several minutes providing simple information to call center personnel, including repeating it several times for verification or because their call has been moved. This process is not only inconvenient for the caller, but it can also be a waste of time and money for your call center! Using smarter technology to limit the quantity of data that must be transmitted is a wonderful approach to improve productivity, efficiency, and customer happiness. It assists in the reduction Our Topics Tags -: ivr solutions in delhi | voice blaster | voice logger | GSM PRI Gateway | GSM VoIP Gateway | Gsm gateway

Users almost always prefer a simple product with fewer features executed extremely well over a feature-bloated product with a lot of capabilities that are executed only marginally well.

Lori Toye founded a small publishing company in August of 1989. Lori Toye's husband joined the team to form I AM America Publishing and Distributing. I AM America Publishing and Distributing has many accomplishments. I AM America publications have been featured on NBC, FOX, UPN, London’s Carlton Television, Art Bell’s Dreamland, George Noory’s Coast to Coast, the Washington Post, and the New York Times.

Teams were involved in creating new technologies, processes, and systems. • Cross-functional teams were formed around new great ideas. • Customers were involved from the inception of each feature concept. It’s important to understand that the old approach did not lack customer feedback or customer involvement in the planning process. In the true spirit of genchi gembutsu, Intuit product managers (PMs) would do “follow-me-homes” with customers to identify problems to solve in the next release. However, the PMs were responsible for all the customer research. They would bring it back to the team and say, “This is the problem we want to solve, and here are ideas for how we could solve it.” Changing to a cross-functional way of working was not smooth sailing. Some team members were skeptical. For example, some product managers felt that it was a waste of time for engineers to spend time in front of customers. The PMs thought that their job was to figure out the customer issue and define what needed to be built. Thus, the reaction of some PMs to the change was: “What’s my job? What am I supposed to be doing?” Similarly, some on the engineering side just wanted to be told what to do; they didn’t want to talk to customers. As is typically the case in large-batch development, both groups had been willing to sacrifice the team’s ability to learn in order to work more “efficiently.

One significant lesson became clear fairly early: each team started out with its own share of dependencies that would hold them back until eliminated, and eliminating the dependencies was hard work with little to no immediate payback. The most successful teams invested much of their early time in removing dependencies and building “instrumentation”—our term for infrastructure used to measure every important action—before they began to innovate, meaning, add new features.

As we continued to meet with Jeff, we tried various kinds of spreadsheets and PowerPoint slides to present and explore our ideas, none of which seemed to be particularly effective. At some point, I don’t remember exactly when, Jeff suggested a different approach for the next meeting. Forget the spreadsheets and slides, he said. Instead, each team member would write a narrative document. In it, they would describe their best idea for a device or service for the digital media business. The next meeting arrived, and we all showed up with our narratives. (As mentioned, ours was one of several teams involved in the early experimentation with narratives at the company. They were not yet official Amazon policy.) We distributed them and read them to ourselves and then discussed them, one after another. One proposed an e-book reader that would use new E Ink screen technology. Another described a new take on the MP3 player. Jeff wrote his own narrative about a device he called the Amazon Puck. It would sit on your countertop and could respond to voice commands like, “Puck. Please order a gallon of milk.” Puck would then place the order with Amazon. The great revelation of this process was not any one of the product ideas. As we’ve described in chapter four, the breakthrough was the document itself. We had freed ourselves of the quantitative demands of Excel, the visual seduction of PowerPoint, and the distracting effect of personal performance. The idea had to be in the writing. Writing up our ideas was hard work. It required us to be thorough and precise. We had to describe features, pricing, how the service would work, why consumers would want it. Half-baked thinking was harder to disguise on the written page than in PowerPoint slides. It could not be glossed over through personal charm in the presentation. After we started using the documents, our meetings changed. There was more meat and more detail to discuss, so the sessions were livelier and longer. We weren’t so focused on the pro forma P&L and projected market segment share. We talked at length about the service itself, the experience, and which products and services we thought would appeal most to the customer.

And when I say “story,” I don’t just mean words. Your product’s story is its design, its features, images and videos, quotes from customers, tips from reviewers, conversations with support agents. It’s the sum of what people see and feel about this thing that you’ve created. And the story doesn’t just exist to sell your product. It’s there to help you define it, understand it, and understand your customers. It’s what you say to investors to convince them to give you money, and to new employees to convince them to join your team, and to partners to convince them to work with you, and to the press to convince them to care. And then, eventually, it’s what you tell customers to convince them to want what you’re selling. And it all starts with “why.

3D printers are already producing parts that are lighter than traditionally built parts, are much stronger in design, and are more readily produced on demand for machines as sophisticated as NASA rockets and Air Force fighters. But for mission-critical products like these, there’s also a risk, one that’s put into context by James Regenor, director of the additive manufacturing and innovation unit at precision parts manufacturer Moog, Inc.: “How can the maintenance crew on a U.S. aircraft carrier have absolute confidence that the software file they downloaded to 3D-print a new part for a fighter jet hasn’t been hacked by a foreign adversary?” To tackle this problem, Regenor’s team at Moog has launched a service it calls Veripart, which uses blockchain technology to, among other things, verify the software design and upgrading work performed by different providers of 3D-printed products along a supply chain. It plans to incorporate a host of features that, among other things, will protect intellectual property and make it more flexible and dynamic as an asset.

We started with a small number of two-pizza teams so that we could learn what worked and refine the model before widespread adoption. One significant lesson became clear fairly early: each team started out with its own share of dependencies that would hold them back until eliminated, and eliminating the dependencies was hard work with little to no immediate payback. The most successful teams invested much of their early time in removing dependencies and building “instrumentation”—our term for infrastructure used to measure every important action—before they began to innovate, meaning, add new features. For example, the Picking team owned software that directed workers in the fulfillment centers where to find items on the shelves. They spent much of their first nine months systematically identifying and removing dependencies from upstream areas, like receiving inventory from vendors, and downstream areas, like packing and shipping. They also built systems to track every important event that happened in their area at a detailed, real-time level. Their business results didn’t improve much while they did so, but once they had removed dependencies, built their fitness function, and instrumented their systems, they became a strong example of how fast a two-pizza team could innovate and deliver results. They became advocates of this new way of working. Other teams, however, put off doing the unglamorous work of removing their dependencies and instrumenting their systems. Instead, they focused too soon on the flashier work of developing new features, which enabled them to make some satisfying early progress. Their dependencies remained, however, and the continuing drag soon became apparent as the teams lost momentum.

The Kindle Press Release Kindle was the first product offered by the digital media group, and it, along with several AWS products, was among the first at Amazon to be created using the press release approach. Kindle was a breakthrough in multiple dimensions. It used an E Ink display. The customer could shop for, buy, and download books directly from the device—no need to connect to a PC or to Wi-Fi. Kindle offered more e-books than any other device or service available at the time and the price was lower. Today, that set of features sounds absolutely standard. In 2007, it was pioneering. But Kindle had not started out that way. In the early stages of its development—before we got started on the press release approach and when we were still using PowerPoint and Excel—we had not described a device that could do all these things from the customer perspective. We had focused on the technology challenges, business constraints, sales and financial projections, and marketing opportunities. We were working forward, trying to invent a product that would be good for Amazon, the company, not the customer. When we wrote a Kindle press release and started working backwards, everything changed. We focused instead on what would be great for customers. An excellent screen for a great reading experience. An ordering process that would make buying and downloading books easy. A huge selection of titles. Low prices. We would never have had the breakthroughs necessary to achieve that customer experience were it not for the press release process, which forced the team to invent multiple solutions to customer problems. (We tell the whole Kindle story in chapter seven.)

Ive’s design team had obsessed over the rounded corners of the phone and become advocates of Bézier curves, a concept from computer modeling used to eliminate the transition breaks between straight and curved surfaces. The Bézier geometry gave the iPhone rounded corners that arched like a sculpture. A standard rounded corner consists of a single-radius arch or a quarter circle, whereas their curves were mapped through a dozen points, creating a more gradual and natural transition. Meanwhile, Forstall used a standard three-point curve in the corners of iPhone apps. Each time Ive opened his iPhone, he could see the difference between the phone’s carefully crafted corners and the software’s clunky corners. He was powerless to change those features because Jobs excluded him from software design meetings. He could only look at them and fume.

There are a few product teams out there that have modified their product roadmaps so that each item is stated as a business problem to solve rather than the feature or project that may or may not solve it. These are called outcome‐based roadmaps.

Our extensive selection ensures your event becomes unforgettable, offering a wide variety of inflatable options to cater to every age group. Explore our Combo Bouncers, featuring a mix of bouncing and climbing then conquer our Obstacle Courses. For our little guests, our Toddler Bounce Houses provide a safe space for bouncing. Our inventory also includes Carnival Games for friendly competitions, Interactives for team-building, and Concession Items to satisfy those post-bounce cravings.

eye combination my mother always made a fuss about. Maybe that’s why my skin crawled every time someone commented on how attractive a couple we were. It was more a reflection on me than us. He lifts his hand and moves my hair off my forehead. The gesture is intimate, but I’m too stunned to stop him. He brushes his thumb over the scar on my temple. “I was worried about you. You wouldn’t let me see you in the hospital. Or after?” A sigh escapes before I can school my features into something a little more… regretful. “Well, I was embarrassed.” That’s a lie. I just didn’t want to face whatever the fuck emotional roller coaster I was riding the last six months. Seriously. My life went from normal to shit in a split second. Adding Jack—and the life that I thought I had, the one that seemed to go up in a puff of smoke when I woke up in the hospital—would’ve been more pain than I was ready to accept. “Violet!” I step away from Jack, ignoring his wounded expression, and turn to my other friends. Half the dance team is here, and they all crowd around me. Someone pulls at my coffee-stained blouse, and another swoops in to clean the floor where my cup dropped. I had forgotten, in my Jack-shock. “Lucky it wasn’t hot.” Willow nudges me. “Luck and I aren’t on speaking terms.” She visited faithfully every day while I was stuck in the hospital. Kept me sane, kept me looped in to the gossip. She’s the only one who knows what I went through, and I’m keeping it that way. I’m not in the habit of airing my dirty laundry—or my newfound nightmares. I’ve been plagued by bright lights, crunching metal, and snapping bones. She rolls her eyes at my luck comment. “You need to change. We’re taking you out.” Oh boy. My first instinct is to say no, but honestly? I could use a bit of normalcy. My therapist—the talk one, not the physical one—said something about getting back into a routine. Well, for the last two years, I’ve gone out with my girls on Friday nights. There’s nothing more normal than that. I’m actually looking forward to it. She leads the way to the bedroom I haven’t been in since… before. She steps aside and lets me do the honors. Opening the door is like cracking into a time capsule. Fucking devastating. Willow stands behind me, her hand on my shoulder, as I stare around at the remnants of the person I used to be. If I wasn’t aware of how different I was after six months away, I am now. Mentally, physically. There are still clothes that I left on the floor. My chair is pulled out and covered in clothes. There’s a pile of books that I had planned to conquer over the summer in the center of the desk. My bed is made. “I kept the door open

Apple employees are spared such intrusions because they are “scared silent.” As Adam Lashinsky reports in Inside Apple, employees know that revealing company secrets will get them fired on the spot. This penchant for secrecy means the small teams that do most of the work at Apple are given only the slivers of information that executives believe they need. A few years ago, we talked to a senior Apple executive who speculated—but, of course, didn’t know—that CEO Tim Cook might be the only person who knew all the major features of the next iPhone.