Showing posts with label Innovation. Show all posts
Showing posts with label Innovation. Show all posts

Friday, December 17, 2010

CROWD SOURCING: LET SOMEONE ELSE DO YOUR JOB?



Crowd sourcing can be looked at as an application of the wisdom of crowds concept, in which the knowledge and talents of a group of people is leveraged to create content and solve problems. Crowd sourcing can be broken down in to three categories: creation (like Wikipedia); prediction (like Yahoo! Buzz); and organization (like Google).

WHAT IS AT STAKE?

Jeff Howe (June 2006) first proposed the idea of Crowd sourcing.” Whether you believe crowd sourcing is a gimmick, or the next big thing, it’s important to note that the idea is still in its early, some would say idealistic, years. How it was proposed, and what it may become, will be largely based on how it is interpreted. “

POINTS ON CROWD SOURCING:

An analogy with outsourcing, in which work previously done by company employees is offered to, and performed, by a group of people on the Internet – the news is, the introduction of financial motivation, on the part of people doing the work, who get paid for performance; the company doesn’t make employees from the crowd.

A new capability brought on by the Internet: the ability to work together to a shared goal without the need of company’s infrastructure.

Mass customization and collective customer commitment, are models of crowd sourcing. In mass customization, the crowd is reacting to an open call to design an individual well; in the second, the main focus of participation of crowd is the selection crowd sourcing (product management) task.

MY OWN VIEWS:

TRUTH: Business-to-business brands are or subject to regulatory requirements and need a different approach.

TRUTH AND GOOD: There are many a consumer-focused brands - these would benefit from a totally open creative process.

TRUTH BUT BAD: Many times crowd sourcing projects are evaluated by the quantity not the quality of received submissions.

TRUTH: There are two perspectives (benefit or disadvantage) about crowd sourcing’ concept: engagement of an undefined group, and uninformed execution.

TRUTH AND GOOD: There’s a delicate balance between encouraging participation and surrendering control. Engaging consumers has always been essential for establishing brands. Of course delivering the process of brand manager to the crowd is another thing altogether.

TRUTH BUT BAD: As it is commonly practiced in the marketing world, crowd sourcing forgoes strategy and outsources execution.

TRUTH: Crowd sourcing works well for large-scale initiatives where gathering data would be otherwise impossible.

TRUTH AND GOOD: One thing is gaining insights into how consumers think about a given brand, but it is not a problem solver.

TRUTH, GOOD OR BAD? The crowd is just another committee that produces results that are incredibly average.


THE FUTURE AND SOME QUESTIONS:

Crowd sourcing and its counterpart, co-creation have started to become business strategies, if not actual models. Diverse companies have aggressively pursued ways in which customers can help create or inspire new products (co-creation). These practices, accelerated by the web and social media, raise all kinds of questions:

Will crowd sourcing and co-creation, actually increase innovation? (Using peoples talent)

Will they reduce the cost of development and design, and along with it, the salaries of people who create for a living?

Will they help in solving those large, unsolvable problems; everything, from health care to education, to global warming?

Will they change the traditional relationships between employers and employees?

Are crowd sourcing and co-creation here to stay, or are they simply convenient alternatives to business as usual in a miserable economy?

Even after the global financial crisis comes to an end, the new marketplaces that support crowd sourcing will continue to evolve, offering more engaging company’s efficient and creative ways; the company will look for help in the crowd.

WHY? If businesses can find access to more ideas for less, they will, down economy or not. AND, today’s customers and prospects, actually want a voice and a say, in influencing a brand and its products.

Tuesday, November 30, 2010

The Paradox of Paradigm



Paradox is
a statement that seems self-contradictory but expresses possible truth. Also it can be something that is contrary to popular opinion.

Paradigm is something that serves as a model or a pattern. It can be a set of assumptions, concepts, values, and practices that constitutes a way of viewing reality for the community that shares them, especially in an intellectual discipline.

Thomas Kuhn (1922-1996),wrote a ground breaking book, “The Structure of Scientific Revolutions”, in which he describes a paradigm as a box in which normal science places all its beliefs, commitments, until a better paradigm emerges. A paradigm shift is when a new breed of extraordinary scientists choose to jump into that newer, better box.

Later, Stephen Covey (1990) wrote about the paradigm shift in the business context.

A paradigm is the conceptual framework upon which we build our world; it is built upon past experiences; if we are not willing to make shifts in our paradigms, we will remain stagnate in our growth; a paradigm shift is a change from one way of thinking to another; it is something that does not happen like self generation it is driven by change.

We could say it is another name for Change, but a paradigm shift goes much deeper, it is about combining change with the challenging of existing assumptions and innovation.

Leaders of cultures recognize that their traditional paradigm is out of date, and perhaps this leads them to assume that a 'paradigm-shift' program will provide the remedy. Culture change is not simply about how you see yourself and others. It is about how the system works, i.e. how we do the work together, rather than how we work together. The paradigm shift is to understand how to act on the organization as a system.

However, initiatives which threaten the current operating culture are typically resisted to extinction, and many initiatives simply bear no relation to the economic performance of the organization.
The most critical thing to understand about a paradigm is that, in a paradigm shift, everything goes back to zero. What does that mean? It means that whatever made you successful in the old paradigm may not even be necessary in the new paradigm.

And here comes the paradox: The paradox is that changing a culture starts with different thinking about the work.

There are two interesting paradoxes: the decision theory paradox and an Economics paradox:
Abilene paradox: People can make decisions based not on what they actually want to do, but on what they think that other people want to do, with the result that everybody decides to do something that nobody really want to do, but only what they thought that everybody else wanted to do.
Allais paradox: A change in a possible outcome, which is shared by different alternatives, affects people's choices among those alternatives; in contradiction with expected utility theory (utility is a measure of relative satisfaction).

Before shifting paradigms we should see that business in general is filled with instances of paradox.

If it would improve performance to do the work differently, how does it mean we should behave? Focusing on behavior without embedding it in a work context creates an entirely new pathology - people try to play a new game.

By contrast, focusing on how we work, anchors improvement in things that are real, and opens the door to working on culture, in a way which has relevance and, more importantly, is palpably relevant.

This new global world surrounds us with paradox. In order for companies to master paradox they must first identify the opportunity it contains.

Some major businesses are developing an e-commerce in order to sell direct, cut costs and eliminate the small businesses. Yet, small businesses represent a very lucrative, high profit margin market for those businesses.

Another paradox is the question “Should you hire the best people?” Sometimes hiring the best people could be your downfall (another paradox).

It all depends on the situation and how you define "best." Should you focus or diversify?” Both, actually (another paradox), diversification can lead to situations where managers ignore the other business lines and pursue their own goals at the expense of company growth as a whole.

Is paradox the new paradigm?

Will future business success depend on the ability of managers and leaders to embrace paradox? Will they succeed holding in their minds two contradictory ideas, each of which can be applied when necessary?

By embracing paradox, managers will lose the half-truth thinking that ignores the context so pertinent to business decisions. These seeming paradoxes often exist, in the first place, only because we try to apply business rules across all contexts.

It is natural that business bears the same tension that pervades everything else in our lives. Economies and ecosystems are filled with examples of competing goals and conflicting ideas that somehow work themselves out to create balance and, in many cases, an optimal situation.

Only when we have understood the paradoxes of business, can we propose a paradigm shift: changing focus could be the key to getting exactly what we were so focused on to begin with.





Sunday, June 6, 2010

56 Reasons Why Most Corporate Innovation Initiatives Fail

56 Reasons Why Most Corporate Innovation Initiatives Fail: "

bad-business.jpg

Innovation is definitely in these days. The word is on the lips of every CEO, CFO, CIO, and anyone else with a three-letter acronym after their name.

As a result, many organizations are launching all kinds of 'innovation initiatives' -- hoping to stir the creative soup.

This is commendable. But it is also, all too often, a disappointing experience

Innovation initiatives sound good, but usually don't live up to expectations. The reasons are many. What follows are 56 of the most common -- organizational obstacles we've observed that get in the way of a company truly raising the bar for innovation.

See which ones are familiar to YOU. Then, sit down with your Senior Team... CEO... innovation committee, or best friend and jump start the process of going beyond these obstacles.

"

Monday, March 1, 2010

Linkedin Q&A

From a friend: Kitty Kelso

Q: What are the core competencies we could expect from a leader in an organisation whose culture is driven by innovation?

In times when a flow of incessant change is driven by a frantic competitiveness; where endless innovation leads to cannibalization of products; when new entrants in niche markets may impose new rules that affect mature markets; whenever that a disruptive change appears in business environments and adds even more uncertainty and entropy, I wonder if the the classic paradigm of an inspirational leader on which we have believed for years is no longer relevant to manage and lead an organisation whose culture should be clearly driven by innovation.

Although one could suggest to Steve Jobs from Apple and to Sergei Bryn and Larry Page from Google like paradigms of a new style of visionary leadership, what are, from your own professional perspective, the core competencies, distinctive personality traits and managerial style, that could differentiate to these leaders, from leaders belonging to more traditional cultures typical in mature organisations?.

As always, your responses will be properly acknowledged.
Octavio

A: Dearest Octavio: My answer is a leader must be driven by passion, direction, and wisdom. A true Visionary Philospher is one in millions; but as you point out, they do exist. What calls a Visionary to action? When all of the details of a goal come together and fit like a puzzel - maybe a 5,000 word puzzel, but nonetheless the project is solid and conficent. I was deemed a Visionary Philosopher by NYTimes testing several years ago. Yes, very high IQ, but moreso were the additional answers to questions that assigned me that title. A Visionary's mind's strengths allow one to think ahead of the game-to imagine or anticipate what should come next in just about any situation. As explained to me, being judged by the IQ quotient or processing information is not the total picture. A true Visionary is also equally skilled in the numberical and verbal universes of the brain, by drawing from multiple sources of information to come up with great ideas. The timelessness of the vision and the balance between other skills (IQ) are what makes the VP. In addition to strengths in math and linguistics, there is a knack for matching and anticipating patterns. These skills and the uncanny ability to detect the underlying blueprint of most of life's situations add the a Visionary Philosopher mind. Plato and Benedict Spinoza along with many free thinkers, lead successfully and memorably. What is so inspiring to a VP is that when the puzzel comes together, it becomes exciting and fun. Up's, down''s - bring them on - just fix the puzzel. Truthfully, very few VP make but a few mistakes overall. I am one of the lucky ones; it is the magic carpet ride! As always,

kk

Monday, June 29, 2009

Melanie Jordan


I met Melanie Jordan through a trusty (at least in my opinion) vehícle: internet.
It would be easier for me to write her link here and let the reader search for further information about the work of someone that really cares about us. Helping everyone to understand the principals of Infopreneurism.

I actually prefer to address these words in an attempt to drive you through this way of earning knowledge and in consequence Money.

What You Know Is Worth more Than You Know™ allows you to discover a new way of sharing expertise regarding each one's activity. It’s a powerful approach that excels your counciousness misspelings about the impact you might have on others (your followers). The ones that seek that specific information, on the Web or in real life.

Seth Godin is telling us that we are living in a tribus modus. I agree. We are organizing our lives and technology misspellings. Finding leaders and followers is becoming an everyday task. This is where the markets currently are: inside your network. This is the market that trusts you. Other martkets a re difficult to conquer and require financial and marketing efforts substancially more expensive.

Melanie main sources of knowledge:
The Podcast
What you Know is worth more
Melanie on Facebook
Melanie on Linkedin


Please feed us back about this article.
Best regards,
MBUintelligence

Sunday, June 28, 2009

Idea Connection – Online Innovation – It’s not a complicated issue


MBUintelligence was invited to take part on this interesting and immense project. Building relationships, communicate the platform and help Spanish companies to achieve short term goals regarding innovation.

We are honoured in participating on such a huge Project, that is growing very fast in a sustainable manner. Visit the Spanish version

Review the Spanish version of the Website. If you find any mistake, please tell us. Visit the international web page

Please feed us back about this article.
Best regards,
MBUintelligence

Thursday, April 9, 2009

Leadership, Intangibles & Talent Review Q1 2009

Hi everyone, the financial crisis is still uppermost in people’ s minds and new ideas and insights in HR are slowly emerging, interestingly not always from organisations which one would term the “HR establishment”. If you are interested in a review of the research and commentary into leadership, intangibles and talent during Q1 2009, feel free to have a look at our work at http://www.fourgroups.com/link/?50
Bruce Lewin

Sunday, April 5, 2009

IT Design Strategy

Design Patterns:

It is a general reusable solution to a commonly occurring problem in software design ,description or template for how to solve a problem that can be used in many different situations.

Use of Design Patterns:

  • Design patterns can speed up the development process by providing tested, proven development paradigms.
  • New Designs are not visible until later in the implementation, Reusing of Design patterns help to prevent this.
Classification of Design patterns:
  • Creational Pattern
  • Structural Pattern
  • Behavioral Pattern
  • Concurrency Pattern
Typical Creational Patterns:
  1. Abstract Factory
  2. Factory method
  3. Builder
  4. Lazy initialization
  5. Object pool
  6. Prototype
  7. Singleton
  8. Multiton
  9. Resource acquisition
1. Abstract Factory Pattern:

It provides a way to encapsulate a group of individual Factory that have a common theme.
Provide an interface for creating families of related or dependent objects without specifying their concrete classes.
Example : 

diagramFactory --> Round , Triangle , Line 
DocumentFactory --> Letter , email, eBook

2.
Factory method Pattern:
Define an interface for creating an object, but let subclasses decide which class to instantiate. Factory Method lets a class defer instantiation to subclasses.
The factory method pattern is an object-oriented design pattern. It deals with the problem of creating objects without specifying the exact class of object that will be created. The factory method design pattern handles this problem by defining a separate method for creating the objects, whose subclasses can then override to specify the derived type of product that will be created.

Example:
ConcreteCreator Inherits Creator; Both will have method factoryMethod () Returns Product.

3. Builder Pattern:
Separate the construction of a complex object from its representation so that the same construction process can create different representations.

The Builder Pattern is a software design pattern. The intention is to abstract steps of construction of object so that different implementations of these steps can construct different representations of objects. Often, the Builder Pattern is used to build Products in accordance to the Composite pattern, a structure pattern.

4.
Lazy initialization Pattern:

In a software design pattern view, lazy initialization is often used together with a factory method pattern. This combines three ideas:
* using a factory method to get instances of a class (factory method pattern)
* storing the instances in a map, so you get the same instance the next time you ask for an instance with same parameter (compare with a singleton pattern)
* using lazy initialization to instantiate the object the first time it is requested (lazy initialization pattern).

5. Object pool Pattern:

An object pool is a set of initialized objects that are kept ready to use, rather than
allocated and destroyed on demand. A client of the pool will request an object from the pool and perform
operations on the returned object. When the client has finished with an object, it returns it to the pool, rather than destroying it. It is a specific type of factory object.

6.
Prototype Pattern:
Specify the kinds of objects to create using a prototypical instance, and create new objects by copying this prototype.
A prototype pattern is a creational design pattern used in software development when the type of objects to create is determined by a prototypical instance, which is cloned to produce new objects. This pattern is used to:
* avoid subclasses of an object creator in the client application, like the abstract factory pattern does.
* avoid the inherent cost of creating a new object in the standard way (e.g., using the 'new' keyword) when it is prohibitively expensive for a given application.

7. Singleton pattern:
The singleton pattern is a design pattern that is used to restrict instantiation of a class to one object.
Ensure a class has only one instance, and provide a global point of access to it.
Example: Only one instance of a database Object

8. Multiton Pattern:
The Multiton pattern expands on the Singleton concept to manage a map of named instances as key-value pairs.
Example: Java Runtime java.lang.runtime

9.
Resource acquisition Pattern:
It is initialization Ensure that resources are properly released by tying them to the lifespan of suitable objects.

Structural Patterns:

Adapter :Convert the interface of a class into another interface clients expect. Adapter lets classes work together that couldn't otherwise because of incompatible interfaces.
Bridge: Decouple an abstraction from its implementation so that the two can vary independently.
Composite: Compose objects into tree structures to represent part-whole hierarchies. Composite lets clients treat individual objects and compositions of objects uniformly.
Decorator : Attach additional responsibilities to an object dynamically keeping the same interface. Decorators provide a flexible alternative to subclassing for extending functionality.
Facade : Provide a unified interface to a set of interfaces in a subsystem. Facade defines a higher-level interface that makes the subsystem easier to use.
Flyweight: Use sharing to support large numbers of fine-grained objects efficiently.
Proxy : Provide a surrogate or placeholder for another object to control access to it.

Behavioral Patterns:

Behavioral design patterns are design patterns that identify common
communication patterns between objects and realize these patterns.
By doing so, these patterns increase flexibility in carrying out this communication.

* Chain of responsibility pattern: Command objects are handled or passed on to other objects by logic-containing processing objects
* Command pattern: Command objects encapsulate an action and its parameters
* Interpreter pattern: Implement a specialized computer language to rapidly solve a specific set of problems
* Iterator pattern: Iterators are used to access the elements of an aggregate object sequentially without exposing its underlying representation
* Mediator pattern: Provides a unified interface to a set of interfaces in a subsystem
* Memento pattern: Provides the ability to restore an object to its previous state (rollback)
* Null Object pattern: designed to act as a default value of an object
* Observer pattern: aka Publish/Subscribe or Event Listener. Objects register to observe an event which may be raised by another object
* State pattern: A clean way for an object to partially change its type at runtime
* Strategy pattern: Algorithms can be selected on the fly
* Specification pattern: Recombinable Business logic in a boolean fashion
* Template method pattern: Describes the program skeleton of a program
* Visitor pattern: A way to separate an algorithm from an object
* Single-serving visitor pattern: Optimise the implementation of a visitor that is allocated, used only once, and then deleted
* Hierarchical visitor pattern: Provide a way to visit every node in a hierarchical data structure such as a tree.



Concurrency Pattern
Object Oriented Design patterns typically show relationships and interactions between classes & objects targeting on the Design problems rather than application problems.

concurrency patterns are those types of design patterns that deal with multi-threaded programming paradigm.

* Active Object
* Balking pattern
* Double checked locking pattern
* Guarded suspension
* Leaders/followers pattern
* Monitor Object
* Read write lock pattern
* Scheduler pattern
* Thread pool pattern
* Thread-Specific Storage
* Reactor pattern

The Active Object design pattern decouples method execution from method invocation that reside in their own thread of control. The goal is to introduce concurrency, by using asynchronous method invocation and a scheduler for handling requests.

The pattern consists of six elements:
* a proxy, which provides an interface towards clients with publicly accessible methods
* an interface which defines the method request on an active object
* a list of pending requests from clients
* a scheduler, which decides which request to execute next
* the implementation of the active object method.
* a callback or variable for the client to receive the result.

The Balking pattern is a software design pattern that only executes an action on an object when the object is in a particular state.

There are some in this field that think this is more of an Anti-Pattern, than a design pattern.
If an object cannot support its API, it should either limit the API so that the offending call is not available or it should …

* be created in a sane state
* not make itself available until it is in a sane state
* become a façade and answer back an object that is in a sane state.

Double-checked locking is a software design pattern also known as "double-checked locking optimization". The pattern is designed to reduce the overhead of acquiring a lock by first testing the locking criterion (the 'lock hint') in an unsafe manner; only if that succeeds does the actual lock proceed.

Guarded suspension is a software design pattern for managing operations that require both a lock to be acquired and a precondition to be satisfied before the operation can be executed. The guarded suspension pattern is typically applied to method calls in object-oriented programs, and involves suspending the method call, and the calling thread, until the precondition (acting as a guard) is satisfied.

In concurrent programming, a monitor is an object intended to be used safely by more than one thread. The defining characteristic of a monitor is that its methods are executed with mutual exclusion. That is, at each point in time, at most one thread may be executing any of its methods. This mutual exclusion greatly simplifies reasoning about the implementation of monitors compared with code that may be executed in parallel.

Monitors also provide a mechanism for threads to temporarily give up exclusive access, in order to wait for some condition to be met, before regaining exclusive access and resuming their task. Monitors also have a mechanism for signaling other threads that such conditions have been met.

Used in Banking Software design to avoid multiple withdraw of amount from same account.

A read/write lock pattern or simply RWL is a software design pattern that allows concurrent read access to an object but requires exclusive access for write operations.

In this pattern, multiple readers can read the data in parallel but an exclusive lock is needed while writing the data. When a writer is writing the data, readers will be blocked until the writer is finished writing.

scheduler pattern is a software design pattern. It is a concurrency pattern used to explicitly control when threads may execute single-threaded code.

The scheduler pattern uses an object that explicitly sequences waiting threads. It provides a mechanism to implement a scheduling policy, but is independent of any specific scheduling policy — the policy is encapsulated in its own class and is reusable.

In the thread pool pattern in programming, a number of threads are created to perform a number of tasks, which are usually organized in a queue. Typically, there are many more tasks than threads. As soon as a thread completes its task, it will request the next task from the queue until all tasks have been completed. The thread can then terminate, or sleep until there are new tasks available.

Please check back again , I would update with examples.
SRINI CENTHALA