The EC Methodology

Each project will have a different definition of success. In almost every case, you’ll need both quantitative and qualitative feedback to assess whether you’ve reached your goals. That’s the final piece of the puzzle. We need to identify metrics that correlate with success and keep track of them.

🆓 Download our free PDF guide:

💻 Connect with us, partner with us, or give us feedback:

🚀 Subscribe to learn more about our process:

🎥 Watch this series as videos on youtube:

📄 Read this series on our blog on Medium:

✉️ Subscribe to our newsletter:

What is The EC Methodology?

A series of short episodes where we talk about our product development workflow at Éphémère Creative.

Raphaël: Welcome back to our
series on EC's methodology.

Last time we talked about preventing
major breakdowns and setting

yourself up for quick recovery.

Today, we'll talk about gathering data
to better understand your progress.

Every project has a different
definition of success.

In almost every case you'll need both
quantitative and qualitative feedback to

assess whether you've reached your goals.

We need to identify metrics that
correlate with success and figure

out how to keep track of them.

There are many types of data that you
could consider for your success metrics.

Here are a few that we like to
consider when building an app.

App data.

This is just the data in your database.

If you're building a task tracking
app, then it might just be the number

of completed tasks and the database.

We like to monitor this type of data, the
data that's in your internal application

database with a tool called Metabase.

Though there are others you could use like
AWS QuickSight or Google's data studio.

Next behavioural data.

This is data gathered from how
your users interact with the app.

This is in contrast with the data
that they actually submit to the app.

For example, it might be which screens
they've visited in a mobile app, or

which pages they visited on a website.

It might also be the things that
they've clicked on or what step

they've reached in a form or a flow.

This is typically collected
using analytics tools.

Some of our favorites include segment,
Google analytics and Mixpanel.

Next up operational data.

This is data like how many features
did we release this quarter?

We like to keep track of that type of
thing in our project management tool.

Currently we're using ClickUp.

But other viable options include
Asana, JIRA, and

Next performance data.

This is the type of data that
we would be pulling from the

tools we discussed last time.

For example, how fast
is everything running?

How many servers are we using?

Or are there crashes
happening on a regular basis?

Alrighty next qualitative feedback.

Feedback from users is crucial to
understanding how well you're doing

and where you need to go in the future.

This is harder to measure,
but it is absolutely crucial.

You need to connect with your users.

This data basically comes from reaching
out to them that could be using automated

systems like Customer IO or Intercom, or
it could be looking at your analytics,

figuring out who are the best users
and reaching out to them directly.

There are definitely other types of data
that you can use to measure success.

But these are the ones
that we use most commonly.

If you found this helpful and you want
to learn more about app development,

make sure to check out our free PDF.

And let us know.

How do you define success in
your apps and how do you measure.

Follow us if you want to keep up with this
series, we have a lot more to share, and

we're always updating our process from
the things that we've learned along the

way and our community and our partners.

If you think that we could work
together, we'd love to partner with you.

Just reach out and we'll see if we can
help you out with your next project.

Thanks and see you next time.