Your SlideShare is downloading. ×

Open Source Business Development

540

Published on

Compared to lots of other open source communities, the WordPress community has a lot to offer. This discussion talks about respecting users, customers, industry stakeholders and community leadership …

Compared to lots of other open source communities, the WordPress community has a lot to offer. This discussion talks about respecting users, customers, industry stakeholders and community leadership while trying to develop a business that operates under the GPL.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
540
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
1
Comments
0
Likes
1
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • "This discussion talks about respecting users, customers, industry stakeholders and community leadership"\n
  • \n
  • target number of customers? customer feedback received? customer profiles? revenue per customer? knowing when something is finished\n
  • copy: define the limitations (features) of the offering\nnotes: great products have a point of view on the problem. asana vs basecamp, heroku vs amazon web services, \n
  • copy: dialing in the narrative: identifying the nearest neighbors, competitors and partners\n
  • copy: the platform is the people, a strength and a weakness\nnotes: there is no such thing as a “platform offering” as such yet, “wp hosting” is not a platform nor an “answer.” right now only the thought leaders, the people are the platform\n
  • copy: the web is built on stacks. WP needs to play it’s role in the stack\nnotes: the future of products / services is in using WP as a component. we deliver products using only the WP UI for example or where WP is extended / complimented by numerous other technologies\n
  • lots of the leaders are solving the same problems because it’s too difficult to give things away\n
  • it’s too difficult to roll new services\n
  • copy: because WP’s not RESTful, innovation in ecosystem has been stifled\n
  • if you haven’t done it before, you probably don’t “get it.” even if you’ve done it before, you still may not “get it”\n
  • copy: reactive “innovation” must be come decisive innovation\nnotes: WP has lead the market offering strong conventions and best practices, but needs to transition to offering raw capability and “starting point” implementations for things like the customizer which could be used for onboarding workflows for theming, extending the 5 minute install or countless other purposes that improve the solid usability improvements that have brought us this far. we need to make complete thoughts and fully learn and understand needs so that we can provide real innovation instead of playing wack-a-mole\n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Transcript

    • 1. Open Source BusinessDevelopment Presented by Frederick Townes
    • 2. AboutCo-founder, PlacesterAdvisor, MashableFounder, W3 EDGE
    • 3. DEFINE LIMITATIONS OF THE OFFERING
    • 4. DIALING IN THE NARRATIVE: IDENTIFYING NEAREST NEIGHBORS, COMPETITORS AND PARTNERS
    • 5. THE PLATFORM IS THE PEOPLE,A STRENGTH AND A WEAKNESS
    • 6. THE WEB IS BUILT ON STACKS.WP NEEDS TO PLAY IT’S ROLE
    • 7. LOTS OF THE LEADERS ARE SOLVING THE SAME PROBLEMS BECAUSE IT’S TOO DIFFICULT TO GIVE THINGS AWAY
    • 8. IT’S TOO DIFFICULT TO ROLL NEW SERVICES
    • 9. IF YOU HAVEN’T DONE ITBEFORE, YOU PROBABLY DON’T “GET IT.” EVEN IF YOU’VE DONE ITBEFORE, YOU STILL MAY NOT “GET IT”
    • 10. REACTIVE“INNOVATION”MUST BECOME DECISIVE
    • 11. Lessons LearnedAnticipate needs and questions
    • 12. Lessons LearnedCollect info before engaging
    • 13. Lessons LearnedExpect tl;dr - be patient
    • 14. Lessons Learned Answer thequestion, don’t editorialize
    • 15. Lessons LearnedThank them for using yoursoftware, even if it’s free
    • 16. Lessons LearnedApologize even ifyou’re not at fault
    • 17. CheersNeed help?innovationredefined@w3-edge.comFollow me@w3edge

    ×