- 30 Jul 2009
- Working Paper Summaries
Fluid Teams and Fluid Tasks: The Impact of Team Familiarity and Variation in Experience
In the context of team performance, common wisdom suggests that performance is maximized when individuals complete the same work with the same people. Although repetition is valuable, at least up to a point, in many settings such as consulting, product development, and software services organizations consist largely of fluid teams executing projects for different customers. In fluid teams, members bring their varied experience sets together and attempt to generate innovative output before the team is disassembled and its individual members move on to new projects. Using the empirical setting of Wipro Technologies, a leading firm in the Indian software services industry, this study examines the potential positive and negative consequences of variation in team member experience as well as how fluid teams may capture the benefits of variation while mitigating the coordination costs it creates. Key concepts include: As organizations continue to depend on the output of teams, and teams, in turn, rely on members with varied prior experience, it becomes critical for teams to manage these differences and dependencies successfully. If the most valuable assets of many companies are their employees, then organizations need to shift from only thinking about their project portfolio to also considering their employee-experience portfolio. Managing employee-experience portfolios will require managers to consider the breadth of types of experience (e.g., customer, technology, etc.) captured across the members of a team as well as their familiarity with each other. Doing so may offer managers an important new lever for improving organizational performance. Closed for comment; 0 Comments.
- 16 Jul 2009
- Working Paper Summaries
Principles that Matter: Sustaining Software Innovation from the Client to the Web
Despite the current strength and promise of the Internet software market, the future pace of growth and innovation is not assured. The principles of choice, opportunity, and interoperability were important in the growth of PC software and in the overall health of the information technology ecosystem, and these same principles will shape competition in Internet software, according to HBS professor Marco Iansiti. Given the unprecedented speed at which this industry is developing, consumers and the industry should watch carefully as different companies compete. Choice, opportunity, and interoperability should serve as an important lens, particularly when focused on companies with especially large footprints in the new markets. Key concepts include: Successful technology companies should not forget that innovation and growth in the technology sector is dependent on promoting a thriving ecosystem of complementary and interdependent products. The competitive principles of choice, opportunity, and interoperability are important in Internet software, because of the increased variety of possible software and hardware combinations and the increased interdependency in the applications and services they deliver. Closed for comment; 0 Comments.
- 28 May 2009
- Working Paper Summaries
Monopolistic Competition Between Differentiated Products With Demand For More Than One Variety
How and when is price competition most significant among firms? This paper develops a theoretical framework for studying price competition between multiple firms. Two examples of markets that fit the description for study are software applications and videogames: There are thousands of software applications as well as games, and different users are interested in different applications and/or games. A given software or game user's tastes may overlap with another's, yet they may have nothing in common with a third's. Thus, although there is a sense in which competition is localized (any given firm competes only with firms whose brands are similar to its own), it is not clear how the fact that consumers are generally interested in purchasing multiple products affects the type of competition waged among firms. Key concepts include: This paper proposes a theoretical framework for studying competition between differentiated products when consumers are interested in purchasing more than one brand. Closed for comment; 0 Comments.
- 14 May 2009
- Working Paper Summaries
Quantity vs. Quality and Exclusion by Two-Sided Platforms
It is common for two-sided platforms to deny participation to some potential customers, who would otherwise be willing to pay the platforms' access and/or transaction fees. Videogame console manufacturers such as Microsoft, Sony, and Nintendo, for example, restrict access to a select set of game developers and exclude many others by including security chips in their consoles, even though the latter would also be willing to pay the per-game royalties levied by the manufacturers. Apple routinely excludes certain application developers from its highly popular iPhone store. Professor Andrei Hagiu builds a simple model formalizing profit-maximizing two-sided platforms' choice of exclusion policies, which is fundamentally determined by a tradeoff between quality and quantity. Key concepts include: A simple model captures the incentives that two-sided platforms have to exclude some participants who would be willing to pay the platform's access fees. Platforms' exclusion incentives are fundamentally determined by a tradeoff between quality and quantity. Closed for comment; 0 Comments.
- 22 Oct 2008
- Working Paper Summaries
Variation in Experience and Team Familiarity: Addressing the Knowledge Acquisition-Application Problem
Team familiarity helps team members successfully locate knowledge within a group, share the knowledge they possess, and respond to the knowledge of others. While team familiarity may help all teams to better coordinate their actions, it may play a particularly important role for teams with individuals looking to apply knowledge from their varied experience. This possibility leads to the question that provides the foundation for this paper: Does team familiarity moderate the relationship between variation in experience and performance? Prior research attempting to link variation in experience and performance has found effects ranging from positive to neutral to negative. Huckman and Staats explain these differential results by drawing on related work from learning, knowledge management, and social networking. Key concepts include: Managers may benefit from a more detailed understanding of the types of experience that are relevant in their setting (e.g., market, technology). If the most valuable assets of many companies are their employees, then organizations may need to shift from thinking about their project portfolio to their employee-experience portfolio. Conditions that assist in the acquisition of useful knowledge, such as variation in experience, will not guarantee—and may even deter—the eventual application of that knowledge. It is important to separate the processes of knowledge acquisition and knowledge application. Closed for comment; 0 Comments.
- 09 Jun 2008
- Lessons from the Classroom
Monetizing IP: The Executive’s Challenge
Many companies fail to develop a strategy around protecting and monetizing their intellectual property. In this Q&A, Harvard Business School professor Josh Lerner discusses current trends in IP including the rise of patent pools. Closed for comment; 0 Comments.
- 14 Apr 2008
- Research & Ideas
The Surprising Right Fit for Software Testing
Software analysts and programmers live to innovate—but hate to run tests. Yet top-notch testing saves many a company money when bugs are caught early. A case study describes the secret behind a Danish consultancy's success: The majority of its testers have Asperger syndrome or a form of autism spectrum disorder. Open for comment; 0 Comments.
- 24 Mar 2008
- Working Paper Summaries
Optimal Deterrence when Judgment-Proof Agents Are Paid In Arrears—With an Application to Online Advertising Fraud
It is commonplace for large entities (both advertisers and ad networks) to enter into relationships with numerous small agents such as Web sites, blogs, search syndicators, and other marketing partners. For example, one well-known affiliate network boasts more than a million affiliates promoting offers from the network's hundreds of merchants, and Google contracts with numerous independent Web sites to show Google's "AdSense" ads. Although these advertising agents are often small, they can take advantage of technology to claim payments they have not earned. In practice, the legal system cannot offer meaningful redress to an aggrieved advertiser or ad network. This paper argues that delayed payment offers a more expedient alternative—a sensible stopgap strategy for use when primary enforcement systems prove inadequate. Key concepts include: Online advertising markets are one of many markets where agents may be effectively unreachable through the legal system. Online advertising contracts presently lack any institution by which the payment structure can enforce good practices. Improving detection technology remains the preferred deterrent of online advertising fraud. Appropriate selection of a payment delay can achieve the benefits offered by contingent payment in other markets. Closed for comment; 0 Comments.
- 24 Mar 2008
- Research & Ideas
Reducing Risk with Online Advertising
Fraud is fairly easy in the world of online advertising, particularly for determined adversaries. In this Q&A, HBS professor Ben Edelman, who designs electronic markets, explains how contract terms can be managed to both reduce advertisers' risks of being defrauded and reward good suppliers. "The idea here is to make everyone better off, except of course the fraudsters," Edelman says. Key concepts include: Delaying payment separates the wheat from the chaff and good affiliates from bad ones. Rule breakers know that the longer they have to wait to be paid, the more likely they are to get caught. In online advertising, it is often hard to know whether you've received the service you've contracted to receive and have paid for. Online affiliate programs are a big source of fraud. Because these programs are perceived to be low-fraud marketplaces, advertisers omit many ordinary protections they use when dealing with little-known suppliers. How to compute the optimal delay for payments is different depending on how prevalent bad affiliates are, the profit margins of bad affiliates, and how quickly your good suppliers need to get paid. Closed for comment; 0 Comments.
- 03 Mar 2008
- Working Paper Summaries
Testing a Purportedly More Learnable Auction Mechanism
Each year, auctions are used to determine how billions of dollars of goods and services will be allocated across the globe. On eBay alone, $52.5 billion in merchandise was exchanged in 2.4 billion auctions conducted during fiscal year 2006. Considerable attention has been paid in the academic literature to the question of how to design auctions with efficient allocation and revenue-maximizing properties. However, in part because auction rules are typically published and standard theory assumes economic agents are capable of computing optimal strategies from published rules, little attention has been paid to the question of how to design auctions whose optimal strategies are easy to learn. Evidence suggests that even when auction rules are published and dominant strategies exist, people nonetheless struggle and sometimes fail to learn to play their optimal strategy. As a result, the authors argue that the question of how to design a learnable, strategy-proof auction mechanism is an important one. Key concepts include: Designers of auction mechanisms should create mechanisms that are easier for people to learn. This paper describes an auction mechanism that has received attention in the computer science literature because of its theoretical property of being more learnable than the standard mechanism. In fact, the new mechanism produced slower learning in human subjects than the standard mechanism. Closed for comment; 0 Comments.
- 24 Jan 2008
- Working Paper Summaries
The Impact of Component Modularity on Design Evolution: Evidence from the Software Industry
What factors should influence the design of a complex system? And what is the impact of choices on both product and organizational performance? These issues are of particular importance in the field of software given how software is developed: Rarely do software projects start from scratch. The authors analyzed the evolution of a commercial software product from first release to its current design, looking specifically at 6 major versions released at varying periods over a 15-year period. These results have important implications for managers, highlighting the impact of design decisions made today on both the evolution and the maintainability of a design in subsequent years. Key concepts include: Data show strong support for the existence of a relationship between component modularity and design evolution. Tightly coupled components have a higher probability of survival as a design evolves compared with loosely coupled components. Tightly coupled components are also harder to augment, in that the mix of new components added in each version is significantly more modular than the legacy design. Closed for comment; 0 Comments.
- 01 Oct 2007
- Working Paper Summaries
Team Familiarity, Role Experience, and Performance:Evidence from Indian Software Services
In contexts ranging from product development to service delivery, a significant amount of an organization's work is conducted by "fluid teams" that strive for innovative output. Fluid project teams exist only for the duration of a single project, and are comprised of members who may join or leave a team during the course of a project. In such settings, simple measures of cumulative output may not accurately capture team experience, particularly when changes in team composition are substantial over time. This study of an Indian software services firm, Wipro Technologies, considers an approach for capturing the experience held by fluid teams. It extends the concept of team fluidity in a way that allows for greater granularity in the measurement of team experience and a finer understanding of the determinants of team performance. Key concepts include: The findings underscore the need to use caution in assuming cumulative output wholly captures experience when team membership is not constant from one project to the next. These results build on previous research on team familiarity by considering longitudinal data on the individual members of teams. The findings also emphasize the importance of considering role experience and studying experience at different levels of seniority. Closed for comment; 0 Comments.
- 13 Aug 2007
- Working Paper Summaries
Diasporas and Domestic Entrepreneurs: Evidence from the Indian Software Industry
Several recent studies have highlighted the important role that cross-border ethnic networks might play in facilitating entrepreneurship in developing countries. Little is known, however, about the extent to which domestic entrepreneurs rely on the diaspora and whether this varies systematically by the characteristics of the entrepreneurs or their local business environment. The Indian diaspora is estimated at over 18 million people spanning 130 countries. Given that formal institutions in India remain weak and hence the informal barriers to trade are higher, do diaspora networks serve as substitutes to the functioning of the local business environment? Do they help entrepreneurs to circumvent the barriers to trade arising from imperfect institutions? This study examines the extent to which software entrepreneurs within India vary in their reliance on expatriate networks. Key concepts include: Entrepreneurs located outside software hubs—in cities where monitoring and information flow on prospective clients is harder—rely significantly more on diaspora networks for business leads and financing. Those who rely more on diaspora networks also have better performing firms. This benefit from the diaspora is stronger for entrepreneurs who are based outside hubs. Benefits from the diaspora accrue most to entrepreneurs who have previously lived abroad and returned to India, compared with those who have not lived abroad. Professional rather than ethnic ties may well form the basis for these networks. Policymakers in developing countries could leverage their diasporas to help with domestic entrepreneurship by developing links between the diaspora and smaller cities rather than with hubs. Closed for comment; 0 Comments.
- 22 Jun 2007
- Working Paper Summaries
Proprietary vs. Open Two-Sided Platforms and Social Efficiency
The rising popularity of the open-source software movement has prompted many governments around the world to enact policies promoting open-source software systems at the expense of proprietary systems. Oftentimes, these policies seem to stem from a presumption (shared by some economists) that open software platforms are inherently more efficient than their proprietary counterparts. But is that so? This paper provides a simple model of two-sided platforms that clearly shows how this common intuition breaks down in two-sided markets. Key concepts include: Proprietary platforms may induce higher levels of product variety, user adoption, and total social welfare than open platforms. Proprietary platforms are sometimes more socially desirable than open platforms, which runs against the common intuition that open platforms are more efficient. Analysis of socially desirable benefits in two-sided markets follows a very different logic from that in one-sided markets, and may lead to counterintuitive conclusions. More in-depth research on the subtler aspects of platform governance in two-sided markets (cooperatives, associations, etc.) should inform both policymakers and business practitioners. Closed for comment; 0 Comments.
- 14 Jun 2007
- Working Paper Summaries
Evolution Analysis of Large-Scale Software Systems Using Design Structure Matrices and Design Rule Theory
Designers have long recognized the value of modularity. But because design principles are informal, successful application depends on the designers' intuition and experience. Intuition and experience, however, do not prevent a company such as Microsoft from constantly grappling with unanticipated challenges and delays in bringing software to market. Clearly, designers need a formal theory and models of modularity and software evolution that capture the essence of important but informal design principles and offer ways to describe, predict, and resolve issues. This paper evaluates the applicability of model and theory to real-world, large-scale software designs by studying the evolution of two complex software platforms through the lens of design structure matrices (DSMs) and the design rule theory advanced by Kim Clark and Carliss Baldwin. Key concepts include: Important software modularity principles have remained informal. DSM models reveal a key characteristic of modular architectures: The design rules must be explicitly defined so that otherwise dependent modules can be decoupled. Each independent module can then be replaced with a better version. DSM modeling and the design rule theory of Clark and Baldwin have the potential to formally account for how design rules create options in the form of independent modules and how they enable independent substitution. DSM modeling and design rule theory are general enough to model decisions other than those encoded in source code. Closed for comment; 0 Comments.
- 07 Mar 2007
- Research & Ideas
How Do You Value a “Free” Customer?
Sometimes a valuable customer may be the person who never buys a thing. In a new research paper, Professor Sunil Gupta discusses how to assess the profitability of a customer in a networked setting—a "free" customer who nevertheless influences your bottom line. Key concepts include: In multi-sided markets, some customers contribute to a company's bottom line directly while others contribute indirect benefits, which are more difficult to calculate. Businesses must be able to assess the value of these "free" customers in order to efficiently allocate marketing and other expenses to grow the business, and to develop a more accurate estimate of firm value. Using a model for valuing networked customers, Gupta found that in an auction scenario, buyers and sellers had almost equal value even though sellers outnumbered buyers 4.6-to-1. Closed for comment; 0 Comments.
- 15 Dec 2006
- Working Paper Summaries
The Business of Free Software: Enterprise Incentives, Investment, and Motivation in the Open Source Community
IBM has contributed more than $1 billion to the development and promotion of the Linux operating system, and other vendors such as Sun are ramping up open source software efforts and investment. Why do information technology vendors that have traditionally sold proprietary software invest millions of dollars in OSS? Where have they chosen to invest, and what are the characteristics of the OSS projects to which they contribute? This study grouped OSS projects into clusters and identified IT vendors' motives in each cluster. Key concepts include: Cluster 1, the "money-driven cluster," consisted of projects that have received almost all of vendor investments. The eighteen projects in this cluster have received over $2 billion in investment. Cluster 2, the "community-driven cluster," has a large number of projects that have received almost no vendor investment. IT vendors have generally ignored projects in this cluster and appear to have no coordinated strategy for dealing with them. Examining the impact of projects in both clusters shows that vendors have not invested uniformly in high-impact OSS projects. Instead, vendors invest in projects that can serve to draw revenues to their own (largely proprietary) core business. Closed for comment; 0 Comments.
- 25 Sep 2006
- Research & Ideas
How Software Platforms Revolutionize Business
Cell phones, the Game Boy, and PCs are examples of products based upon software platforms—ecosystems where independent companies can provide products and services tied to the core technology. Playing in a software platform world can make you rich—ask ringtone creators—but it also demands special management skills that emphasize cooperation over competition. Professor Andrei Hagiu discusses his new book, Invisible Engines. Key concepts include: Software platforms have improved productivity and innovation in many industries, disrupted or destroyed others, and created entirely new businesses. Software platforms are powerful engines of change because of the malleability of code and of the fundamental functions they perform, which make it easy for them to march across industry boundaries; and because their multi-sided nature allows them to spawn vibrant ecosystems of complementors. Managing software platforms is about much more than creating technology. It takes skills in navigating cooperation and competition, building creative business models, and anticipating competition across industries. Closed for comment; 0 Comments.
- 05 Jul 2006
- Working Paper Summaries
Exploring the Structure of Complex Software Designs: An Empirical Study of Open Source and Proprietary Code
How does a product's design mirror the organization that develops it, and how does such a dynamic occur? To track the evolution of one design over time, this exploratory study compared software designs developed via different modes of organization-open source versus proprietary development. As it turned out, the architecture of the product developed by a highly distributed team of developers (Linux) was more modular than another product of similar size developed by a co-located team of developers (Mozilla). The study helped reveal potential performance tradeoffs from architectures with different characteristics. Key concepts include: The value of design is a managerial choice. There are important, measurable differences in modularity between different software systems of comparable size and function. Systems may vary dramatically in terms of their robustness to change, and the costs and efficiency of future enhancements. Closed for comment; 0 Comments.
Mixing Open Source and Proprietary Software Strategies
Open source and proprietary software development used to be competing strategies. Now software firms are experimenting with strategies that mix the two models. Researcher Gaston Llanes discusses recent research into these "mixed source" strategies. Key concepts include: Software companies are taking a "best of both worlds" approach by creating products that use a combination of OS and proprietary software code. The researchers wanted to get a clearer sense of when a profit-maximizing firm should adopt a mixed-source business model and what that model might look like under different circumstances. Results indicate recurring patterns and strategies that managers can take into consideration when setting strategy. Closed for comment; 0 Comments.