Create a digital "roll" with friends. Take pictures from the roll. You can't see them until: the roll is used up, a time limit expires, or you get to a specific location.
Great thread full of potential https://t.co/jA8h08M48z ideas! 💡
Create a digital "roll" with friends. Take pictures from the roll. You can't see them until: the roll is used up, a time limit expires, or you get to a specific location.
Send a guest a video or audio clip asking a question. Guest replies when able with same medium. Repeat. When done, share produced video/podcast.
A web app to track the progress of your project: ideation, naming, shipping code, launching.
Page can also be a dynamic browser overlay for live streaming.
Have tools for polls, surveys, sharing, launching to various outlets, etc.
If health insurance screws you over, no one has your back but you. Instead, can pay a small monthly fee to a service to take care of BS like this for you should issues arise.
Find local/regional businesses, gyms, co-working, cafés, etc. that offer discounts for digital nomads or van lifers. Akin to Epic Pass.
Send URLs and/or pictures of recipes to service and receive a simple, well formatted/standard book, catalog or cue cards in box of those recipes.
Simple site for displaying a company's first sale (like framed dollar bills in small businesses).
More from Tech
A common misunderstanding about Agile and “Big Design Up Front”:
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.
There’s nothing in the Agile Manifesto or Principles that states you should never have any idea what you’re trying to build.
You’re allowed to think about a desired outcome from the beginning.
It’s not Big Design Up Front if you do in-depth research to understand the user’s problem.
It’s not BDUF if you spend detailed time learning who needs this thing and why they need it.
It’s not BDUF if you help every team member know what success looks like.
Agile is about reducing risk.
It’s not Agile if you increase risk by starting your sprints with complete ignorance.
It’s not Agile if you don’t research.
Don’t make the mistake of shutting down critical understanding by labeling it Bg Design Up Front.
It would be a mistake to assume this research should only be done by designers and researchers.
Product management and developers also need to be out with the team, conducting the research.
Shared Understanding is the key objective
I\u2019d recommend that the devs participate directly in the research.
— Jared Spool (@jmspool) November 18, 2018
If the devs go into the first sprint with a thorough understanding of the user\u2019s problems, they are far more likely to solve it well.
Big Design Up Front is a thing to avoid.
Defining all the functionality before coding is BDUF.
Drawing every screen and every pixel is BDUF.
Promising functionality (or delivery dates) to customers before development starts is BDUF.
These things shouldn’t happen in Agile.
