crowdSPRING Blog

JULY 2, 2018

Web browsers weren’t really designed to handle apps that stay open all day long. Its simple design hides a lot of features, including some robust collaboration tools like chat (video, audio, and text), as well as sharing and collaborating on lists. Using these apps in a web browser, however, can be a pain. Cost: Free.

Product 69

Product Web Wiki Design 69

Startup Lessons Learned

AUGUST 8, 2009

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The argument itself got me thinking a lot about design and its role in building products.

Software Review 87

Software Review Design Software San Francisco 87

Startup Lessons Learned

AUGUST 30, 2008

Lessons Learned by Eric Ries Saturday, August 30, 2008 Refactoring for TDD and interaction design In TDD , we follow a rhythm of “test-code-refactor.&# The same process works in Interaction Design. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. April 23, 2010 in San Francisco.

Software Review 74

Software Review San Francisco Design Continuous Deployment 74

crowdSPRING Blog

JULY 2, 2018

Web browsers weren’t really designed to handle apps that stay open all day long. Its simple design hides a lot of features, including some robust collaboration tools like chat (video, audio, and text), as well as sharing and collaborating on lists. Using these apps in a web browser, however, can be a pain. Cost: Free.

Product 48

Product Web Wiki Design 48

Startup Lessons Learned

FEBRUARY 23, 2013

This is especially true when designing a great product. What follows is an excerpt from Chapter 4 (Collaborative Design) of Lean UX: Applying lean principles to improve user experience by Jeff Gothelf and Josh Seiden The most effective way I’ve found to rally a team around a design direction is through collaboration.

Lean 167

Lean Software Review Wiki Design 167

YoungUpstarts

JUNE 25, 2012

An example is Matt, a mid manager working in a science museum who used unauthorised tools like Google calendar for scheduling, Flickr for sending photos, wikis for collaboration and a self-made YouTube video for fundraising. These worked far better than what corporate could dish out.

Software Review 145

Software Review Wiki Social Network Leadership 145

Both Sides of the Table

NOVEMBER 1, 2009

We spent time out in the marketplace talking with customers, looking at their solutions, comparing ourselves with our competition and then squirreling ourselves away in our offices designing our next set of features. He published our first wiki where the whole list of potential features were outlined. He’s a smart guy.

Customer 280

Customer Technical Review Software Review Mexico 280

Startup Lessons Learned

JANUARY 12, 2010

The Lean Startup Wiki (hosted by long-time lean startup pbWorks) contains a number of resources, including links to case studies , meetups, tools , and people who have volunteered to help. Its a wiki, feel free to consume and enhance it. Its a wiki, feel free to consume and enhance it. April 23, 2010 in San Francisco.

Lean 146

Lean San Francisco Wiki Startup 146

Both Sides of the Table

AUGUST 23, 2010

The design, albeit not intuitive at first, was beautiful and in weird ways very graceful. And they are trying to bake in user adoption into the design of the product. It also feels very wiki like. But still … with blogging being my priority it was hard to commit the hours to Quora.

Silicon Valley 301

Silicon Valley Pre-Money Valuation Technical Review Software Review 301

VC Cafe

APRIL 30, 2023

Conduct research Just launched: an agent specifically designed for research. Here’s how it’s going so far (+$217.85) and the strange ways it’s saving money. (1/n): 1/n): pic.twitter.com/JO9p1A5ipc — Joshua Browder (@jbrowder1) April 29, 2023 2.

Generative AI 183

Generative AI ChatGPT Artificial Inteligence API 183

Steve Blank

MARCH 8, 2011

It was designed to bring together many of the new approaches to building a successful startup – customer development, agile development, business model generation and pivots. The first class was an introduction to the concepts of business model design and customer development. Start their blog/wiki/journal for the class.

Lean 298

Lean Business Model Customer Development Guinea 298

YoungUpstarts

OCTOBER 19, 2011

Send students on an assignment in the library, asking them to go on a treasure hunt for QR codes hidden in the library, following clues through wikis and webpages. Architecture professors could tag campus buildings with QR codes, sharing their history and design with students. Digital discoveries in the library. Digital portfolios.

Software Review 211

Software Review Technical Review Mobile Video 211

Austin Startup

AUGUST 18, 2010

One promising direction involves leveraging established wiki techniques crowdsource raw data, in a way that supports collaboration over the structure and schema of the data as well as its values and instances. It was a simple and extremely powerful idea, and SMW now encompasses an active worldwide developer community.

Semantic 86

Semantic Web Wiki Metadata 86

Feld Thoughts

JUNE 22, 2012

Wikipedia was a tremendous invention in the process of knowledge curation, and it was dependent, in turn, on the invention of wikis. A documentation system such as a wiki is useless without any way to access it. I chose to use computers I owned that were designed for compactness for their time. But I digress…).

Artificial Inteligence 182

Artificial Inteligence Technical Review Bandwidth Software Review 182

Steve Blank

DECEMBER 7, 2010

Or more accurately, startups are a temporary organization designed to search for a scalable and repeatable business model.) There are few courses which teach aspiring entrepreneurs the skills (business models, customer and agile development, design thinking, etc.) Start your blog/wiki/journal. Update your blog/wiki/journal.

Wiki 311

Wiki Lean Management Business Model 311

steveblank.com

JULY 8, 2011

Github - Free public repositories, collaborator management, issue tracking, wikis, downloads, code review, graphs Pivotal Tracker – Agile project management tool that enables real time collaboration. WebSequenceDiagrams - sketch sequence diagrams.

Software Review 110

Software Review Startup Silicon Valley Analytics 110

VC Cafe

NOVEMBER 1, 2019

How does the design make me feel? A quick look at what’s available shows they are targeting enterprise users (design, product, sales, human resources, engineering…) but the Personal and Education template libraries are also fairly developed. I enjoy the process of trying new products like a kid opening a birthday present.

Wiki 68

Wiki San Francisco Post-Money Valuation Cloud 68

Austin Startup

SEPTEMBER 18, 2017

They will manage the steps necessary to identify, select, and integrate your software and IT vendors, including third party product dependencies, email, network, wiki, intranet, project management, and telecommunications. Voltage Control specializes in Innovation Workshops such as Design Sprints. Please email douglas@voltagecontrol.co

Fractional CTO 54

Fractional CTO CTO Hire CTO Technical Review 54

ConversionXL

JANUARY 12, 2017

When sites are designed, developed and written with web accessibility in mind, everyone has equal access to online information, products, and opportunities. For example, a key principle of Web accessibility is designing Web sites and software that are flexible to meet different user needs, preferences, and situations. Guideline 1.4:

Web 48

Web Software Review Technical Review Canada 48

YoungUpstarts

AUGUST 26, 2015

Well-designed intranet platforms offer a case feature that can be opened up and used as tickets for internal or external issues, such as a bug or a customer support request. For example, if a user has created a Wiki, than they will receive a notification every time someone else updates that Wiki. Cases, Issues, or Tickets.

Wiki 100

Wiki Thailand Campaign Community 100

Startup Lessons Learned

MARCH 25, 2010

for Harvard Business Review) Over at Harvard Business Review, Ive been building up a series designed to introduce the Lean Startup methodology to a business-focused audience. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Lessons Learned by Eric Ries Thursday, March 25, 2010 Speed up or slow down?

Software Review 141

Software Review San Francisco Lean Continuous Deployment 141

Startup Lessons Learned

OCTOBER 5, 2008

These specs are handed to a designer, who builds layouts and mockups of all the salient points. Then the designs are handed to a team of programmers with various specialties. The programmers keep asking for more say in the designs and direction that they work on. First, he writes it nice and clear.

San Francisco 158

San Francisco Management Software Review Product 158

crowdSPRING Blog

MAY 8, 2015

We just love sharing articles about fonts, logo design , web design , startups, entrepreneurship, small business, leadership, social media, marketing, economics and other interesting stuff! 6 problems with motion design education bit.ly/1GFKNZI. Logo Design: Music Instruments bit.ly/1PYBNTL.

Small Business 48

Small Business Design Social Media Startup 48

Startup Lessons Learned

JANUARY 18, 2010

If youre interested in contributing a case study for publication here, consider getting started by adding it to the Lean Startup Wiki case study section. Prior to starting any maker activity, I clearly identify what needs to get done (the goal) and sketch out how it needs to get done (the design).

Continuous Deployment 151

Continuous Deployment San Francisco Lean Wiki 151

Startup Lessons Learned

APRIL 4, 2010

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

Agile 99

Agile San Francisco Software Review Continuous Deployment 99

www.readwriteweb.com

APRIL 24, 2012

Equally important, Wordpress is more popular than all other content-management stems combined , with massive networks of developers, designers and SEO experts ready to help out at a moments notice. List Yours, Find Others' on This Wiki. startup tools wiki. Cormac Foster. Lead image courtesy of Shutterstock. and tagged with.

Startup 53

Startup Wiki Semantic RSS 53

Startup Lessons Learned

FEBRUARY 20, 2009

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Similar results apply in product management, design, testing, and even operations. Take the example of a design team prepping mock-ups for their development team. I dont think so.

San Francisco 161

San Francisco Software Review Continuous Deployment Development Team Review 161

ReadWriteStart

JANUARY 29, 2013

Work fast, track competitors and design a great icon. Chris Kohlhardt co-founded Gliffy in 2005 to provide an easy way to embed diagrams within wikis, and today users can create org charts, Venn diagrams, flowcharts, floorplans and other diagrams via its Web service, and embed them within Word 2013, Google Docs or Atlassian Confluence.

Wiki 60

Wiki Software Software Engineering Algorithm 60

Startup Lessons Learned

JULY 29, 2009

Like a financial debt, the technical debt incurs interest payments, which come in the form of the extra effort that we have to do in future development because of the quick and dirty design choice. We can choose to continue paying the interest, or we can pay down the principal by refactoring the quick and dirty design into the better design.

Technical Review 168

Technical Review Software Review San Francisco Lean 168

Startup Lessons Learned

NOVEMBER 6, 2008

They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Anyway, thanks Stevey for your thoughtful post. April 23, 2010 in San Francisco. Bring your questions.

Agile 76

Agile San Francisco Software Review Continuous Deployment 76

Startup Lessons Learned

AUGUST 3, 2009

Revisiting the Software Design Manifesto (and what. Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco.

San Francisco 168

San Francisco Product Lean Continuous Deployment 168

Spencer Fry

FEBRUARY 13, 2023

When considering our product development process and track record, however, I simply don’t see the value in the work that they would bring to our team that a developer, designer, or head of product can’t drive themselves. Below you’ll find a copy of the Champion position as outlined in our internal wiki. What’s the Champion role?

Product 72

Product Wiki Developer Hiring 72

Software By Rob

APRIL 7, 2010

Not automating this process creates the ongoing repetitive work that computers are designed to handle. Curious if you like that more formal approach or if you’re a bigger fan of freeform text on a wiki… Great piece of advice tho. Automation Now as a developer, the features I mentioned above seem like a necessity from day.

Agile 42

Agile Software Review Wiki Hosting 42

dontbesoanalytical.blogspot.com

MAY 13, 2012

Consider how firms today confront Web 2.0 – the combination of blogs, wikis, and social networking technologies sprouting up. Of course, this draconian measure does not work; employees can blog under another name, or contribute to a wiki pseudonymously. data center design. (1). View my complete profile. ancient artifact.

CTO 40

CTO Technical Review Technology Software Review 40

Startup Lessons Learned

AUGUST 2, 2008

Lean Startup Wiki - including a complete list of local meetups and meetup organizers. Startup Lessons Learned season two : Every post from the blogs second year in print form. Startup Lessons Learned for Kindle Startup Lessons Learned - the conference. April 23, 2010 in San Francisco. Bring your questions.

San Francisco 125

San Francisco Software Review Technical Review Continuous Deployment 125

Startup Lessons Learned

SEPTEMBER 27, 2010

This is precisely the dilemma that the doctrine of minimum viable product is designed to solve. When people start using quality, reliability, or design as an excuse to delay, it used to make me nervous, even when these suggestions were well intentioned. Rules of thumb can be infuriatingly unhelpful. And it’s really hard.

San Francisco 167

San Francisco Lean Continuous Deployment Software Review 167

Startup Lessons Learned

SEPTEMBER 15, 2008

The new design improved on the old one in several ways, but these improvements didnt translate all the way through the funnel. Usually, I think that means youve lost some good aspect of the old design. The designers might be telling you that the new design looks much better than the old one, and thats probably true.

San Francisco 166

San Francisco Lean Technical Review Continuous Deployment 166