Check out all our ‘HipTips’ blogs

Stand up! How remote teams perform daily standups

| May 15, 2017

Anyone who works remotely knows the importance of staying in sync with teammates—to push through roadblocks, avoid duplicate work, and share updates. “Standups”—a daily routine in which every team member shares their progress—have become popular amongst technical teams, but the truth is that any and every team can (and will) benefit, especially dispersed teams.

Read more →

I sent 3 emails in 1 month—here’s how

, Product Marketing | April 28, 2017

HipChat was never created to be an email killer. For many teams—and even my teammates—email still holds important benefits. But for me, the need for email is (almost) dead.

Read more →

4 HipChat features you should be using, but (maybe) aren’t

| April 28, 2017

There are a bunch of ways HipChat saves you time and mental energy, so you can be as productive as possible. Here are 4 of our favorites—if you’re not using them, you’re missing out on some of the simplest yet most effective features we’ve got!

Read more →

Get started with ChatOps in 3 simple steps

, Product Marketing | March 29, 2017

You spend half your day communicating with your team in chat and the other half jumping between other apps, browser tabs, and email chains. If you’ve ever thought there must be a better way, you’re right on the money. Today’s technology offers the advantage of bringing all your team’s important information into one cohesive workflow. We call this ChatOps.

Read more →

5 simple ways your IT team can embrace ChatOps

, Product Marketing | March 28, 2017

As an IT professional, you’re all about creating the fastest, smoothest, most forward-thinking solutions. Being on the cutting edge of technology, you may have heard of this ChatOps thing a time or two. Joining your everyday tasks with your everyday communications in one central hub—what could be simpler or more potent than that?

Read more →

4 tips for scaling your business from a few to many

| March 21, 2017


This is a guest blog post by Jack Saville, Online Marketer at Bynder.

When a company grows from tens to hundreds of employees in a short period of time, there are bound to be growing pains. How do people meet and work closely together? How does company culture thrive? At Bynder, a digital asset management provider, we faced these questions head-on—growing from 50 to 250 employees in two years.

As hard as growing can be, we’ve found some simple ways to scale our business and maintain our core values. Here are some nuggets of wisdom we’d love to share.

Read more →

Meet Polly Bot: Add polls to your rooms

| March 14, 2017

Where should your team meet after work for drinks? What color should your T-shirts be? Who should be your team’s mascot? You’ve all got opinions, and Polly Bot keeps tally of them so your team can make a decision. Create the poll, monitor it, and shut it down—all within your HipChat room.

Read more →

Better Python Testing: How to Mock AWS [video]

, HipChat DevOps Engineer | March 08, 2017

At Atlassian, my fellow engineers and I often find ourselves creating tools that rapidly become crucial to our own workflows. Because of this, the practice of writing tests to ensure consistent behavior is almost second nature for us.

We’re aware that this is not the case for everyone.

Read more →

Putting the “me” in “team”: how to personalize your HipChat apps

| February 28, 2017

You’re a team player, and you put the team first. But to be a great team player, you first have to look out for yourself. We’ve designed HipChat for individuals who build out a team—which means you should be setting up your HipChat integrations and workflow so it works best for you.

Read more →

Don’t go down the rabbit hole: Use room READMEs

| February 16, 2017

If Alice had had a README to reference down in Wonderland, she wouldn’t have had to figure out what “Eat me” and “Drink me” would lead to via trial and error. Same goes in HipChat. Ever entered a room and not known its purpose? Or not known if you’re meant to be there? Room READMEs solve this.

Read more →