Skip to content

Update/Expand What Section of README.md issue #9#13

Merged
iteles merged 28 commits intomasterfrom
update-what-section-issue#9
Nov 11, 2019
Merged

Update/Expand What Section of README.md issue #9#13
iteles merged 28 commits intomasterfrom
update-what-section-issue#9

Conversation

@nelsonic
Copy link
Copy Markdown
Member

@nelsonic nelsonic commented Nov 4, 2019

This Pull Request Addresses the question raised by @Cleop in issue #9 💭

I feel these docs are more readable now.
@iteles Please review and give feedback if possible.

@nelsonic nelsonic added the in-progress An issue or pull request that is being worked on by the assigned person label Nov 4, 2019
@nelsonic nelsonic self-assigned this Nov 4, 2019
@nelsonic nelsonic added the T4h Time Estimate 4 Hours label Nov 5, 2019
@nelsonic nelsonic mentioned this pull request Nov 9, 2019
6 tasks
@nelsonic nelsonic added awaiting-review An issue or pull request that needs to be reviewed and removed T4h Time Estimate 4 Hours in-progress An issue or pull request that is being worked on by the assigned person labels Nov 9, 2019
@nelsonic nelsonic requested a review from iteles November 9, 2019 21:44
@nelsonic nelsonic assigned iteles and unassigned nelsonic Nov 9, 2019
@nelsonic nelsonic marked this pull request as ready for review November 9, 2019 21:44
@nelsonic
Copy link
Copy Markdown
Member Author

nelsonic commented Nov 9, 2019

@iteles if/when you have time, please review and give any feedback. Thanks. 📥

…on/answer to end of README.md as it breaks the flow #9
@iteles iteles added in-review Issue or pull request that is currently being reviewed by the assigned person and removed awaiting-review An issue or pull request that needs to be reviewed labels Nov 10, 2019
Copy link
Copy Markdown
Member

@iteles iteles left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@nelsonic This is fantastic, thank you for capturing all this (hahaha)

There are 2 comments about typos but the rest of my comments are just notes about things I would like to add myself in the coming days.

Do you want to correct these 2 typos before I merge the PR? Or shall I go ahead and merge and then I can correct them asap when submitting my next PR?

on working towards the collective ***goal***.
Having a _clear_ **Product Roadmap** is ***essential***
to help ***everyone*** _focus_
on our collective **goal**.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍 A fan of how succinct this 'why' is

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, had to tighten it. 👍

and/or guarding the user-feedback,
they are _stuck_ in the _old_ mindset.

they are _stuck_ in a _fixed_ mindset.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I want to add something in here about how the goal is not to safeguard our own profits or ability to make money. We need to be sustainable but the more people working towards a world where people are not overwhelmed, riddled with anxiety and always lifting each other up, the better.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iteles agree with the sentiment of putting people before profit while being sustainable. 👍
I feel that is more suited to https://github.com/dwyl/start-here/blob/master/manifesto.md 💭

Public on GitHub is a good or bad idea, we think it's
worth the _experiment_ just to discover the outcome.

### Why Do So _Few_ Companies Make Their "Road Map" Public?
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like that this was removed. I think it distracts from the main message and the two paragraphs above say all that is needed in a much more concise way 👍

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iteles moved to the end of the doc; not removed entirely.

README.md Outdated
whereas a reading list item could be "daily commute"<br />
**d)** **Add** any additional ***detail*** you can think of at the time.
e.g: acceptance criteria, deadline, dependencies <br />
**d)** If the item is a task that has sub-tasks, create and link them.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be e.
Also, Linking them definitely belongs here but splitting a task out into actionable steps doesn't really belong here. It will evolve.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iteles indeed it will evolve rapidly. 🐎
My aim was merely to address #9 and clarify What we are building in the MVP phase. 👍

**d)** **Add** any additional ***detail*** you can think of at the time.
e.g: acceptance criteria, deadline, dependencies <br />
**d)** If the item is a task that has sub-tasks, create and link them.
3. ***Complete*** - do the work to _complete_ the item/task.<br />
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a very big section. Whereas the first 2 'C's are small, independent actions, this one can involve a lot of different steps and take a long time depending on dependencies (i.e. if you're not doing the work yourself or waiting for bureaucracies). We'll eventually need to split this out but it doesn't have to be done now.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iteles yeah, the first two steps are relatively succinct and the third is where the real work is done.
I very much want the Product Manager/Owner to take responsibility for the "Workflow" and get feedback from people using the app. Ultimately the App will succeed (or fail) based on the simplicity (or complexity) of the workflow (getting the text of a "brain dump" to be a task/reminder/etc. and then getting it to done as effectively as possible)
image

README.md Outdated
will be _personalised_ to the individual
based on the features they (_most_) _use_.
If the person does not _use_ a particular function, they won't _see_ it.
> Note: This is might not feel relevant during "MVP",
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙌 This will of course be coupled with a discovery section where people can take a look at other features

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. That's going to be one of our USPs. Each feature will have a walkthrough demo/video that will explain why the feature exists, who it's for and how to use it. 💡

1. **Use** the **_Beta_ App**!
`[insert app link here!]`
2. Give us ***feedback*** on the **_existing_ UX**
`[insert feedback link here!]`
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎉

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coming very soon ... 😉

README.md Outdated

#### MVP Basic Workflow

+ [ ] Mobile First UI/UX to **Capture** **`plaintex`**
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

plaintext (also needs correcting in the lines below)

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

plaintex -> plaintext typos fixed in 3 instances. thanks for spotting. 👍

of everything that is occupying space and processing power
is _essential_ for gaining focus
on the _one_ most important priority.
This step is often referred to as a "brain dump".
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add a note here also about how having a trusted place to keep all of your thoughts is the only way to truly empty your mind. If you have scattered post-it's or a system that makes it difficult to view what needs to be done, the fear of forgetting something keeps everything in RAM anyway.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iteles yes, please refine as you see fit. 📝
My objective was just to get something down for the PM/PO to work with. 👍

of capturing free text (_using a **`textarea`** element_)
and safely storing it as **`text`** in Postgres.

Figma wireframe: https://www.figma.com/proto/WrpkKGJNYZbeCzMRDVtvQLbC/dwyl-app
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How do we signal that we have finished typing and want to move onto the next item?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iteles iteles removed the in-review Issue or pull request that is currently being reviewed by the assigned person label Nov 10, 2019

And finally for the _third_ step, ***Complete***,
we will build a simple checklist system.
See: [`checklists.md`](https://github.com/dwyl/product-roadmap/blob/master/checklists.md)
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've noticed a few typos on the checklist document, I'll create a new PR to fix them.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SimonLab yes, please do fix when you have time. thanks. 👍

README.md Outdated



### USP: What is _different_ about the @dwyl App?
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

image

Sub title not displayed correctly. Looking why it's broken.

Also the USP meaning wasn't obvious to me and had too google it. We can write it down fully (Unique Selling Point/Proposition) or link it to the wikipedia page: https://en.wikipedia.org/wiki/Unique_selling_proposition

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SimonLab please edit it to help clarify it for others. thanks. 👍

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry just saw the link to the Wikipedia page just under.

@SimonLab
Copy link
Copy Markdown
Member

As you've seen ⬆️ I've added a few suggestions to fix some typos.

I'm not sure yet about the USP title yet but hopefully it will be displayed properly.
The other thing I've noticed is the link to the "work hard every waking hour" youtube video is not working anymore:
image

We can either remove the link or try to find a new link to the video.

Otherwise looks good 👍

@nelsonic
Copy link
Copy Markdown
Member Author

@SimonLab thanks for taking the time to review this PR in such great detail and propose changes. 👍
Lame that the video link is broken ... 😞
Alternative link to Elon Musk "work hard every waking hour": https://youtu.be/liJbB_0eCTo?t=25 📺

I'm a fan of Elon's work ethic and feel that it will inspire/motivate others in our community,
so I'm keen to keep the reference. I'm really not a fan of people who do the bare minimum work and think it's important to set expectations. Note: Not saying that everyone needs to work 80-100 hours per week like Elon. People should decide for themselves what they want in life. If they want "balance" in their 20's more than early retirement in their 30's that's their decision. Nothing "wrong" with it. 👍

Copy link
Copy Markdown
Member

@SimonLab SimonLab left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great, @iteles I'll let you check one last time if you want and merge the PR?

@SimonLab SimonLab assigned iteles and unassigned SimonLab Nov 11, 2019
@iteles
Copy link
Copy Markdown
Member

iteles commented Nov 11, 2019

👍 Thanks both!

@iteles iteles merged commit bb3888c into master Nov 11, 2019
@iteles iteles deleted the update-what-section-issue#9 branch November 11, 2019 13:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

in-review Issue or pull request that is currently being reviewed by the assigned person

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants