Tracking Changes in WorkFlowy (à la MS Word) – Viewing Markup, Your Final Draft or the Original Text

A post by Frank Degenaar (@ProMashUp), author of the highly acclaimed book, “Do Way, Way More in WorkFlowy”.

I’m about to walk you through a very real, very useful use case of mine for collaborating in WorkFlowy. If you’ve ever used MS Word’s “Track Changes” tool, you’ll want to bookmark this post for the next time you’re editing someone else’s work in WorkFlowy… That is, if a WorkFlowy user who’s text you’re editing cares to compare the original, the marked up revision and the final draft of their work. Continue reading “Tracking Changes in WorkFlowy (à la MS Word) – Viewing Markup, Your Final Draft or the Original Text”

Collaborating in WorkFlowy – The Proof is in the Pudding

A post by Frank Degenaar, author of the book,“Do Way, Way More in WorkFlowy”.

You might be collaborating quite satisfactorily with one tool or another – but until you start collaborating directly in WorkFlowy, you’ll never know how miserably one dimensional everything else is.

The uniqueness and power of collaborating in WorkFlowy – as opposed to tools like Email, Google Docs, Slack, Trello and Evernote – is this: Not only do we (1) get to organize our collaborative efforts any which way we choose in one infinitely nest-able outline – but we also have the ability to (2) comment and input information concurrently into any part of our outline and (3) filter for any “updates” anywhere in a snap. These are just the broad strokes.

Here’s a must-read comment from Ksenia. She puts it better than I ever could!

I still use Email and Slack. Of course. But WorkFlowy has become indispensable to me over the last year since I started blogging in this space and collaborating with scores of WorkFlowy users. This is no small thing. The proof is in the pudding. It’s time to climb aboard this train and try some collaborative pudding in the dining car. Continue reading “Collaborating in WorkFlowy – The Proof is in the Pudding”

The Explanation For Our Recent Downtime

Summary: I got a false alert that the issues were resolved. Foolishly, I didn’t look into it further and didn’t realize we had an ongoing outage. 

My deepest apologies for the two outages we’ve had in the past day. The first happened yesterday at around 5pm pacific time, the second today at around 6am.  Both were caused by the same simple, easy to resolve issue. In both cases, I did not resolve the issue causing the outage because I didn’t realize the outages were happening. Our monitoring system sent me alerts saying the issues had resolved themselves just moments after it pointed out the problems in the first place. I should have looked into the issues upon getting the alerts, regardless of their supposed resolution, and I didn’t. Thus, we had hours of downtime when we should have had minutes.

I am ashamed of the situation, and stressed by the potential repercussions on the trust of our users. Due to my actions, tens of thousands of people around the world were blocked from doing their work over the past day. My apologies to all of you.

Here is what I will do to prevent this happening in the future:

  1. I’ve added two new alerts to our monitoring which are direct indicators of our most common issues. These metrics will not incorrectly resolve themselves while an outage remains active.
  2. I will always look into outage alerts, even if I get an automated alert saying an issue is resolved.
  3. After an alert, I will look at our core metrics dashboards as opposed to my own app responsiveness to determine whether the app is healthy. Loading the home page is an incredibly dumb way to verify the health of our servers. I did it simply because I was away from my computer and have never seen a real outage falsely resolved  without additional alerts. That was a huge mistake.
  4. After an alert, I will monitor our user communication channels such as Twitter and email, to get a sense of how widespread an issue is.

Again, I am truly sorry for these completely unnecessary outages. We will do our best to maintain our previously wonderful reliability.

P.S. Please consider using our offline Chrome Desktop Application. This way you will have access to your WorkFlowy lists even if we have an outage, or if you’re away from the internet.

The Power of Reading Books in WorkFlowy

A post by Frank Degenaar, author of the book,“Do Way, Way More in WorkFlowy”.

I’ve read over a dozen books in WorkFlowy so far. But why? Why in blue blazes would I do that? Simple, really: For the unparalleled flexibility WorkFlowy gives me in being able to turn any scrap of information therein into a #todo, a #reminder or a research #category… and being able to take notes to my heart’s content – so that it all becomes part of my workflow.

If you haven’t yet put a book into WorkFlowy, it’s a crying shame: You’ve been missing out on possibly the most effective way to (1) act upon gems of information being provided and (2) to glean, gather and group research data in the simplest of ways. Hands down, reading and interacting with book content in WorkFlowy is the most intuitive way I’ve found to squeeze every ounce of practical worth out of any book. Continue reading “The Power of Reading Books in WorkFlowy”

Create a Customer Service Database in WorkFlowy – Don’t Throw Away Your Hard Work!

A post by Frank Degenaar, author of the book,“Do Way, Way More in WorkFlowy”.

I’m fast, but not that fast:

— “Dad, how many days until Christmas?”
— “About 6 months sweetheart.”
— “But how many days?”
— “About 180 da… wait… Siri, how many days until Christmas?”
— [Sexy monotone voice] “It’s one hundred seventy-eight days until then.”

… so I put the tools at my disposal to work for me: I could work things out in my head, but there’s an easier way. An easier workflow.

In a similar fashion, I could frantically hammer away at my keyboard only to repeat the same customer service information that’s been asked many times before (and which will certainly be asked many times over in the days to come)… or I could get a game plan together and have the previous answer(s) at my fingertips, ready to go – cut with the very same cookie cutter.

It feels really good to work smarter and save time. This brief post is about setting up a simple system (in WorkFlowy) to capture the insightful solutions and information that we already have in our head – so that we don’t have to type them out all over again, from scratch. Continue reading “Create a Customer Service Database in WorkFlowy – Don’t Throw Away Your Hard Work!”

Give Me One Good Reason Why You’re Not Creating Lists WITH Your Kids

A post by Frank Degenaar, author of the book,“Do Way, Way More in WorkFlowy”.

I’ve dedicated my WorkFlowy book to my daughter:

For Emma-Pearl: Each Pomodoro spent on this book meant less beach time for you. Though you don’t yet know all about lists and productivity, you’re on almost all of my lists… and hands down, the #1 beneficiary of my @Future-me tag.

I’m going to need to change this up a tad, because my daughter has caught on to list making in a big way since my book came out. I’m kicking myself for not having taught her about making lists much sooner. You know… little human beings are much more capable than we give them credit for. If you’re not making lists with your kids yet, you’re seriously missing out – it’s so much freaking fun!

Continue reading “Give Me One Good Reason Why You’re Not Creating Lists WITH Your Kids”

Picking Names out of a WorkFlowy Hat

A post by Frank Degenaar, author of the book,“Do Way, Way More in WorkFlowy”.

Pens and random scraps of paper are getting scarcer by the day. And we don’t always just happen to have a hat at hand… but at social events (even in these ever-so-modern times), we still do keep up with drawing straws, picking names out of a hat… and Secret Santa.

What we all do have at hand is a smartphone. Oh yes… and we have WorkFlowy. With about a minute of pre prep-work, you can show off how smart (and sophisticated) you are – and digitize this most basic of human practicalities. What you are about to witness is the reconstruction of a true story, which occurred on December 24th of 2015, at around midnight. I’ve only changed up the names. Obviously. Continue reading “Picking Names out of a WorkFlowy Hat”